System, method and user interface for supporting scheduled mode changes on electronic devices

ABSTRACT

An electronic device configures the electronic device to operate in a first mode, when the current time is with a first scheduled sleep time period, and user input selecting an affordance using a first input mechanism is disabled in the first mode. While in the first mode, detecting first user input. The electronic device transitions the electronic device into a second mode different from the first mode if the first user input meets predefined criteria, and remains in the first mode and forgoes transitioning to the second mode if the first user input does not meet the predefined criteria.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 63/023,214, filed May 11, 2020, which is incorporated herein byreference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for supporting scheduled modechanges on electronic devices, such as scheduled mode changes thatcorrespond to a sleep schedule established on the electronic devices.

BACKGROUND

The use of portable electronic devices has increased significantly inrecent years, with many applications typically residing in the memory ofsuch devices. Example applications include communications applications(e.g., messaging and telephone), calendar applications, newsapplications, media playback applications (e.g., podcast, music, andvideo), payment applications, reminder applications, social mediaapplications, and service delivery applications. These applicationsgenerate events, which contain information of varying degrees ofimportance to users. Notifications that correspond to the generatedevents may be displayed. Example notifications include digital images,video, text, icons, control elements (such as buttons) and/or othergraphics to notify users of events. Example applications that generatenotifications include messaging applications (e.g., iMessage or Messagesfrom Apple Inc. of Cupertino, Calif.), calendar applications (e.g., iCalor Calendar from Apple Inc. of Cupertino, Calif.), news applications(e.g., Apple News from Apple Inc. of Cupertino, Calif.), media playbackapplications (e.g., Podcasts, Apple Music and iTunes from Apple Inc. ofCupertino, Calif.), payment applications (e.g., Apple Pay from AppleInc. of Cupertino, Calif.), reminder applications (e.g., Reminders fromApple Inc. of Cupertino, Calif.), social media applications, and servicedelivery applications.

BRIEF SUMMARY

Conventionally, a user may utilize an electronic device to set up a waketime alarm using an alarm application, manually enabling a Do NotDisturb (DND) mode of the electronic device using a settingsapplication, and/or enable sleep quality tracking using a healthapplication, etc. But current user interfaces for establishing a sleepschedule and related functions are cumbersome and inefficient. Forexample, to enable the different functions related to sleep, the devicerequires the user to use different applications that do not coordinatetheir operations. To establish or modify some sleep-related functions,some devices require the user to navigate to obscure, hard-to-findsettings user interfaces of the devices' operating systems. At thepresent, there is no simple way for a user to easily establish and/oradjust the functions related to a user's sleep schedule. Existingmethods take longer than necessary, thereby wasting energy. This latterconsideration is particularly important in battery-operated devices.

As described above, some techniques for establishing and adjustingfunctions related to a sleep schedule using electronic devices aregenerally cumbersome and inefficient. For example, some existingtechniques use a complex and time-consuming user interface, which mayinclude multiple key presses or keystrokes. Existing techniques requiremore time than necessary, wasting user time and device energy. Thislatter consideration is particularly important in battery-operateddevices.

Accordingly, the present technique may provide electronic devices withfaster, more efficient methods and interfaces for establishing andadjusting functions related to a sleep schedule. In addition, thepresent technique may enable additional functions that promotes user'scompliance of an established sleep schedule and improve the user'sexperience when using the electronic device to support his/her sleepschedule. Such methods and interfaces optionally complement or replaceother methods for establishing and adjusting functions related to asleep schedule, promoting user's compliance of the established sleepschedule, and improving the user's experience when using the electronicdevice to support his/her sleep schedule. Such methods and interfacesmay reduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated computing devices, suchmethods and interfaces may conserve power and increase the time betweenbattery charges.

In some embodiments, a device implementing the present techniques is adesktop computer. In some embodiments, the device is portable (e.g., anotebook computer, tablet computer, or handheld device). In someembodiments, the device is a personal electronic device (e.g., awearable electronic device, such as a watch). In some embodiments, thedevice has a touchpad. In some embodiments, the device has atouch-sensitive display (also known as a “touch screen” or “touch-screendisplay”). In some embodiments, the device has a graphical userinterface (GUI), one or more processors, memory and one or more modules,programs or sets of instructions stored in the memory for performingmultiple functions. In some embodiments, a user interacts with the touchscreen GUI primarily through stylus and/or finger contacts and gestureson the touch-sensitive surface. In some embodiments, a user interactswith the touch screen GUI of the device to perform or enable functionsthat optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, digital video playing, and system level operations, such asdisplaying a home screen, locking a device, displaying a system-levelnotification screen, displaying a system-level control panel userinterface, etc. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at anelectronic device including a display generation component and one ormore input devices. The method includes, displaying, via the displaygeneration component, a respective user interface that corresponds to arestricted state of the computer system, including: in accordance with adetermination that a current time is outside of a first preset timeperiod preceding or following a scheduled mode change for the computersystem, displaying a first user interface that corresponds to therestricted state of the computer system; and in accordance with adetermination that the current time is within the first preset timeperiod preceding or following the scheduled mode change, displaying asecond user interface that corresponds to the restricted state of thecomputer system, the second user interface being different from thefirst user interface. The method further includes, while displaying therespective user interface that corresponds to the restricted state ofthe computer system, detecting a first input directed to the respectiveuser interface; in response to detecting the first input directed to therespective user interface: in accordance with a determination that thefirst input meets first criteria, and that the first user interface wasdisplayed when the first input was detected, replacing display of thefirst user interface with a third user interface that is different fromthe first user interface and the second user interface; and inaccordance with a determination that the first input meets secondcriteria different from the first criteria, and that second userinterface was displayed when the first input was detected, replacingdisplay of the second user interface with display of the first userinterface.

In accordance with some embodiments, a method is performed at anelectronic device including a display generation component and one ormore input devices. The method includes, in accordance with adetermination that a current time is within a first preset time periodpreceding a scheduled mode change and in accordance with a determinationthat a first battery level is below a first preset battery level,displaying, via the first display generation component, a reminder forincreasing the first battery level above the first preset battery level;and in accordance with a determination that the current time is outsideof the first preset time period preceding the scheduled mode change andin accordance with a determination that the first battery level is belowthe first preset battery level, forgoing display of the reminder forincreasing the first battery level above the first preset battery level.

In accordance with some embodiments, a method is performed at anelectronic device including a display generation component and one ormore input devices. The method includes, displaying a first userinterface for specifying a sleep schedule, the first user interfaceincluding one or more user interface objects that are configured toreceive user inputs that specify at least one of a start time and an endtime of a first scheduled sleep period for the sleep schedule. Themethod further includes receiving, via the first user interface, a firstuser input that specifies a first time value that specifies at least oneof the start time and the end time of the first scheduled sleep periodfor the sleep schedule; in response to receiving the first user input:in accordance with a determination that a duration of the firstscheduled sleep period that is determined based on the first time valueis below a preset threshold duration, displaying a first visualindication that the duration of the first scheduled time period is belowthe preset threshold duration, wherein a first value is selected for afirst display property of the first visual indication while the durationremains below the preset threshold duration; and in accordance with adetermination that the duration of the first scheduled time period thatis determined based on the first time value is at or above the presetthreshold duration, displaying, a second visual indication that theduration of the first scheduled time period is meets the presetthreshold duration, wherein a second value, different from the firstvalue, is selected for the first display property of the second visualindication while the duration remains at or above the preset thresholdduration.

In accordance with some embodiments, a method is performed at anelectronic device including a display generation component and one ormore input devices. The method includes, in accordance with adetermination that a current time is within a first scheduled sleep timeperiod of an active sleep schedule, configuring the computer system tooperate in a first mode, wherein user input selecting an affordanceusing the first input mechanism is disabled in the first mode. Themethod further includes, while the electronic system is in the firstmode, detecting, via the second input mechanism, first user input; andin accordance with a determination that one or more characteristics ofthe first user input meet a set of one or more predefined criteria,transitioning the computer system into a second mode different from thefirst mode, wherein user input selecting an affordance using the firstinput mechanism is enabled in the second mode; and in accordance with adetermination that the one or more characteristics of the first userinput do not meet the set of one or more predefined criteria, remainingin the first mode and foregoing transitioning the computer system intothe second mode.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensities of contacts with the touch-sensitive surface,optionally one or more tactile output generators, one or moreprocessors, and memory storing one or more programs; the one or moreprograms are configured to be executed by the one or more processors andthe one or more programs include instructions for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a non-transitory computer readablestorage medium has stored therein instructions, which, when executed byan electronic device with a display, a touch-sensitive surface,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, and optionally one or more tactile outputgenerators, cause the device to perform or cause performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, a touch-sensitive surface, optionally one or moresensors to detect intensities of contacts with the touch-sensitivesurface, optionally one or more tactile output generators, a memory, andone or more processors to execute one or more programs stored in thememory includes one or more of the elements displayed in any of themethods described herein, which are updated in response to inputs, asdescribed in any of the methods described herein. In accordance withsome embodiments, an electronic device includes: a display, atouch-sensitive surface, optionally one or more sensors to detectintensities of contacts with the touch-sensitive surface, and optionallyone or more tactile output generators; and means for performing orcausing performance of the operations of any of the methods describedherein. In accordance with some embodiments, an information processingapparatus, for use in an electronic device with a display, atouch-sensitive surface, optionally one or more sensors to detectintensities of contacts with the touch-sensitive surface, and optionallyone or more tactile output generators, includes means for performing orcausing performance of the operations of any of the methods describedherein.

Thus, electronic devices with displays, touch-sensitive surfaces,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, optionally one or more tactile outputgenerators, optionally one or more device orientation sensors, andoptionally an audio system, are provided with improved methods andinterfaces for navigating between user interfaces and interacting withcontrol objects thereby increasing the effectiveness, efficiency, anduser satisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for establishing andadjusting functions related to a sleep schedule.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 4C illustrates a personal electronic device in accordance with someembodiments.

FIG. 4D is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 4E-4F illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 4G-4J illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 5A-5AE illustrate example user interfaces for providing enhancedaccess restriction during a preset time period before and/or after ascheduled mode change, in accordance with some embodiments.

FIGS. 6A-6D are flowchart diagrams of a method of providing enhancedaccess restriction during a preset time period before and/or after ascheduled mode change, in accordance with some embodiments.

FIGS. 7A-7J illustrate example user interfaces for generating batterycharging alerts during a preset time period before the start of thescheduled mode change, in accordance with some embodiments.

FIGS. 8A-8B are flowchart diagrams of a method of generating batterycharging alerts during a preset time period before the start of thescheduled mode change, in accordance with some embodiments.

FIGS. 9A-9AG illustrate example user interfaces for providing a visualalert when a duration of a sleep time period is adjusted by a user belowan established sleep goal, in accordance with some embodiments.

FIGS. 10A-10C are flowchart diagrams of a method of providing a visualalert when a duration of a sleep time period is adjusted by a user belowan established sleep goal, in accordance with some embodiments.

FIGS. 11A-11AF illustrate example user interfaces for disabling andenabling an input mechanism of an electronic device during a scheduledrestricted mode, in accordance with some embodiments.

FIGS. 12A-12D are flowchart diagrams of a method of disabling andenabling an input mechanism of an electronic device during a scheduledrestricted mode, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing sleep schedules and related functions,promoting user's adherence to the established sleep schedules, andimproving user's experience using the electronic device to managehis/her sleep quality. Such techniques can reduce the cognitive burdenon a user who accesses event notifications, thereby enhancingproductivity. Further, such techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 4C-4J provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 5A-5AE illustrate example user interfaces forproviding enhanced access restriction during a preset time period beforeand/or after a scheduled mode change, in accordance with someembodiments. FIGS. 6A-6D are flowchart diagrams of a method of providingenhanced access restriction during a preset time period before and/orafter a scheduled mode change, in accordance with some embodiments. Theuser interfaces in FIGS. 5A-5AE are used to illustrate the processesdescribed below, including the processes in FIGS. 6A-6D. FIGS. 7A-7Jillustrate example user interfaces for generating battery chargingalerts during a preset time period before the start of the scheduledmode change, in accordance with some embodiments. FIGS. 8A-8B areflowchart diagrams of a method of generating battery charging alertsduring a preset time period before the start of the scheduled modechange, in accordance with some embodiments. The user interfaces inFIGS. 7A-7J are used to illustrate the processes described below,including the processes in FIGS. 8A-8B. FIGS. 9A-9AG illustrate exampleuser interfaces for providing a visual alert when a duration of a sleeptime period is adjusted by a user below an established sleep goal, inaccordance with some embodiments. FIGS. 10A-10C are flowchart diagramsof a method of providing a visual alert when a duration of a sleep timeperiod is adjusted by a user below an established sleep goal, inaccordance with some embodiments. The user interfaces in FIGS. 9A-9AGare used to illustrate the processes described below, including theprocesses in FIGS. 10A-10C. FIGS. 11A-11AF illustrate example userinterfaces for disabling and enabling an input mechanism of anelectronic device during a scheduled restricted mode, in accordance withsome embodiments. FIGS. 12A-12D are flowchart diagrams of a method ofdisabling and enabling an input mechanism of an electronic device duringa scheduled restricted mode, in accordance with some embodiments. Theuser interfaces in FIGS. 11A-11AF are used to illustrate the processesdescribed below, including the processes in FIGS. 12A-12D.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures) asinput. In some embodiments, the one or more input devices are integratedwith the computer system. In some embodiments, the one or more inputdevices are separate from the computer system.

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) containsinformation (e.g., values) that relates to the distance of objects in ascene from a viewpoint (e.g., a camera, an optical sensor, a depthcamera sensor). In one embodiment of a depth map, each depth pixeldefines the position in the viewpoint's Z-axis where its correspondingtwo-dimensional pixel is located. In some embodiments, a depth map iscomposed of pixels wherein each pixel is defined by a value (e.g.,0-255). For example, the “0” value represents pixels that are located atthe most distant place in a “three dimensional” scene and the “255”value represents pixels that are located closest to a viewpoint (e.g., acamera, an optical sensor, a depth camera sensor) in the “threedimensional” scene. In other embodiments, a depth map represents thedistance between an object in a scene and the plane of the viewpoint. Insome embodiments, the depth map includes information about the relativedepth of various features of an object of interest in view of the depthcamera (e.g., the relative depth of eyes, nose, mouth, ears of a user'sface). In some embodiments, the depth map includes information thatenables the device to determine contours of the object of interest in az direction.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 4C illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 4D depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 2200-2500(FIGS. 22-25). A computer-readable storage medium can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 4D, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 4C-4D).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 4E illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 4E additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.4F illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 4E-4F can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 4E-4F to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 4G-4J illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 4G, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 4J. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 4H-4J. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 4G-4J to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 4H. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 4I. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 4J. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 4H-4I, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 4G-4J can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 5A-5AE illustrate example user interfaces for providing enhancedaccess restriction (e.g., providing an additional screen-restricted userinterface (e.g., a wind down screen, a good morning screen, etc.) that,when dismissed by a predefined gesture, navigates to anotherscreen-restricted user interface (e.g., a wake screen, lock screen,etc.)) during a preset time period before and/or after a scheduled modechange (e.g., during a preset wind down period immediately preceding ascheduled sleep time period, or a preset time period immediatelysucceeding the scheduled sleep time period, etc.), in accordance withsome embodiments.

FIGS. 5A1-5L illustrate exemplary interactions with user interfaces fora restricted state of a computer system, e.g., electronic device 100with a touch-screen display 112. In the restricted state, the computersystem prevents access to the home screen and user interfaces ofapplications by displaying a respective user interface that correspondsto the restricted state (e.g., a wake screen in either the authenticatedstate or the unauthenticated state, a lock screen, etc.). In someembodiments, during a preset period before or after a scheduled modechange (e.g., a wind down period or a wind up period for a preset sleeptime period), a special user interface that corresponds to therestricted state (e.g., a wind down screen, a good morning screen, etc.)is displayed, where the special user interface that corresponds to therestricted state requires a dismissal input that is different from theinput used to dismiss a regular user interface that corresponds to therestricted state (e.g., a wake screen or lock screen that is displayedoutside of the wind down period, wind up period, or sleep period); and,upon dismissal of the special user interface that corresponds to therestricted state, the computer system displays the regular userinterface that corresponds to the restricted state. In some embodiments,if the computer system is locked again after the regular user interfacethat corresponds to the restricted state was dismissed and access to thehome screen and/or application user interfaces were obtained, thecomputer system redisplays the special user interface that correspondsto the restricted state when the display is woken again. In someembodiments, automatically (e.g., without user input) providing a winddown screen and/or a good morning screen during a preset time periodbefore and/or after a scheduled sleep period helps to reducedistractions caused by the computer system, and to promote bettercompliance with the sleep schedule and improve users' sleep qualityduring the sleep period. In some embodiments, the computer systemmaintains a Do Not Disturb mode during the preset time period before thescheduled sleep time period, during the scheduled sleep time period,during a preset time period after the scheduled sleep time period, orany combination thereof, to help the user relax and enjoy better sleep.In the following illustrated example, the user has established a sleepschedule for the current day (e.g., Tuesday) that has a sleep timeperiod with a start time of Tuesday 10:00 PM and an end time ofWednesday 6:30 AM, and that has a wind down mode enabled for a timeperiod that begins at 9:00 PM and ends at the start of the sleep timeperiod. In this example, a good morning period or wind up period is alsoenabled that starts from the wake time of Wednesday 6:30 AM and ends atWednesday 9:30 AM.

FIGS. 5A-1-5A-4 illustrate an exemplary input for waking a displaygeneration component of a computer system from a low power or dormantstate during a wind down period (e.g., a preset time period) thatimmediately precedes an upcoming scheduled sleep period for a sleepschedule. In some embodiments, the computer system is a device 100 witha touch screen 112. In some embodiments, the wind down period is enabledby a user during a set up process for a sleep schedule. In FIGS.5A1-5A-2, a user raises the device 100 (e.g., with the user's hand 5002)while the device 100 is in a low power or dormant state (e.g., with adark screen or dimmed always-on screen). As illustrated, before thecriteria for waking the device is met, the touch screen 112 remains inthe low power or display-off state. As the device is raised more towardthe user, as shown in FIGS. 5A-3 and 5A-4, the touch screen 112 is nolonger in the low power of display-off state. Instead, the wake screenuser interface for the wind down mode (e.g., the wind down screen 5013)is displayed when the touch screen 112 is in a regular display-on state.In some embodiments, the wind down screen 5013 is optionally displayedwhen the touch screen 112 is in an unauthenticated state andsubsequently transitions into an authenticated state (e.g., withauthentication information obtained through fingerprint sensors orfacial recognition, etc.) while the user is raising the device 100 orholding the device 100. In some embodiments, the wind down screen 5013is a lock screen, requiring authentication information to be providedonce the wind down screen 5013 is dismissed in order to dismiss theregular lock screen and put the touch screen 112 in an unlocked state.

FIG. 5B shows the device 100 in a low power or dormant state during awind down period (e.g., a preset time period) that immediately precedesan upcoming scheduled sleep period for a sleep schedule. Thetouch-screen of the device 100 is in a display-off state or a low-poweralways-on state. FIG. 5B illustrates alternative ways of waking thedisplay generation component of the computer system during the presetwind down period immediately preceding the upcoming scheduled sleepperiod. For example, the device 100 detects a tap input by a contact5010 on the touch-screen 112, a button press input by a contact 5008 ona power button or screen-lock button 5006 of the device 100, or movementof the device toward a user (e.g., detected based on a determinedorientation of the device or an image captured by a front-facing cameraof the device); and in response, the touch-screen transitions out of thelow power or dormant and displays the wind down screen 5013 on the touchscreen 112, as shown in FIG. 5C.

FIG. 5C illustrates an exemplary wind down screen 5013 on device 100that is displayed during a wind down period (e.g., between 9:00 PM and10:00 PM on Tuesday) preceding a scheduled sleep period (e.g., ascheduled time period from Tuesday night at 10:00 PM to Wednesdaymorning at 6:30 AM). On the wind down screen 5013, a set of userinterface objects are displayed, including a time and date element 5012showing the current time (e.g., 9:41 PM) and the current date (e.g.,Tuesday, March 22). The wind down screen 5013 also displays a bedtimereminder 5020 that displays the start time of the upcoming sleep period(e.g., a textual or graphic indicating the bedtime of 10:00 PM). In someembodiments, the wind down screen 5013 displays an indicator 5011indicating that Do Not Disturb mode is currently active during the winddown period. In some embodiments, when Do Not Disturb mode is active,various types of alerts and notifications that are generated byapplications and the operating system during a normal operation mode aresuppressed. In some embodiments, a small set of critical alerts arestill permitted and generated during the Do Not Disturb mode, such aswake alarms, emergency alerts, etc. In some embodiments, certain typesof output modes (e.g., audio outputs, vibration outputs, etc.) areoptionally disabled during the Do Not Disturb mode, allowing only lowimpact output modes (e.g., tactile outputs, low-volume audio alerts,etc.) to be generated for the small set of critical alerts that arepermitted during the Do Not Disturb mode. In some embodiments, thedevice 100 displays a visual DND indicator persistently on the displayduring a time period that that the Do Not Disturb mode is active.Optionally, minimal affordances for activating one or more functions ofthe device 1000 are provided on the wind down screen, e.g., affordance5014 for activating a flashlight function and affordance 5016 foractivating a camera application may be provided on the wind down screen.In some embodiments, no other actions are made available on the wakescreen user interface (e.g., in the case where no shortcuts toapplication functions (e.g., actions) are enabled for the wind downperiod).

Gestures that are usually used to dismiss a regular wake screen or lockscreen of the device 100 (e.g., regular gestures for navigating from theregular wake screen or lock screen to a user interface that displaysreceived notifications, a user interface that displays widgets, or ahome screen user interface, a last displayed application user interface,etc.) may be ignored by the device 100. As shown in FIG. 5C, a rightwardswipe input by a contact 5022 on the touch screen 112 that normallycauses navigation from a regularly wake screen to a widget screen thatlists widgets for applications on the device is ignored and does notcause navigation away from the wind down screen 5013. An upward edgeswipe gesture by a contact 5024 on the touch screen 112 that normallycauses dismissal of the regular wake screen user interface andnavigation to the home screen user interface or a last displayedapplication user interface (and optionally an authentication userinterface (e.g., a password entry user interface) before the home screenuser interface or last displayed application user interface, if the wakescreen is in an unauthenticated state (e.g., a lock screen)) is ignoredand does not cause navigation to the home screen or last displayedapplication user interface (and optionally does not cause display of theauthentication user interface).

In some embodiments, a predefined input is required to dismiss the winddown screen 5013. In the example user interface of FIG. 5D, a dismissbutton 5018 is included on the wind down screen 5013. A tap gesture 5026on the dismiss button is required to dismiss the wind down screen andnavigate to the regular wake screen. In some embodiments, other types ofpredefined inputs (e.g., a predefined movement pattern, a touch-holdinput followed by the upward edge swipe input, etc.) are required todismiss the wind down screen to navigate to the regular wake screen orlock screen user interface 5025, as shown in FIG. 5E.

In FIG. 5E, while the device 100 displays a regular wake screen or lockscreen 5025 during the wind down period, the device 100 detects agesture that is normally used to dismiss the regular wake screen or lockscreen 5025 to navigate to the home screen or last displayed applicationuser interface. For example, the device 100 detects an upward edge swipeinput by a contact 5028 while the regular wake screen or lock screen5025 is displayed (e.g., while the current time is still within the winddown period, and the wind down mode is still active (e.g., as indicatedby the DND indicator 5011)), as shown in FIG. 5E, and in response to theupward edge swipe gesture by the contact 5028, the device 100 dismissesthe regular wake screen or lock screen 5025 and navigates to anauthentication user interface 5027 (e.g., because the device is in anunauthenticated state), as shown in FIG. 5F. In FIG. 5F, authenticationinformation (e.g., passcode entered by contact 5030) is provided throughthe authentication user interface 5027, and the device 100 verifies thereceived authentication information, changing the device state toauthenticated and navigates to the home screen user interface 5029, asshown in FIG. 5G. In some embodiments, the authentication user interface5027 is not displayed, and the device 100 directly navigates from theregular wake screen 5025 to the home screen 5029, if authentication isautomatically obtained by the device 100 through other mechanisms (e.g.,facial recognition, fingerprint, retina scan, etc.).

From the home screen user interface 5029 shown on FIG. 5G, the user caninteract with the device 100 as normal. For example, the device 100detects a user input by a contact 5031 on the application icon 480 of amusic application in FIG. 5G. In response, as shown in FIG. 5H, thedevice 100 replaces display of the home screen user interface 5029 withan application user interface 5036 of the music application. Whiledisplaying the music application user interface 5036, the device 100detects a press input by a contact 5032 on the button 5006. In someembodiments, the button 5006 is a lock button that locks the device 100and optionally causes the touch screen 112 to transition into a lowpower or dormant state. In some embodiments, a different user input isdetected that locks the device 100. In the example shown in FIG. 5I, thecurrent time is still during the wind down period preceding the upcomingsleep period. As shown in FIGS. 5G-5I, the Do Not Disturb indicator 5011is persistently displayed on the touch screen indicating that the winddown mode is still active during this time.

In FIG. 5I, after the device 100 has returned to a restricted stateduring the wind down period (e.g., in response to the press input bycontact 5032 on the lock button 5006), or woken from the low power ordormant state (e.g., in response to a tap input on the display, anotherpress input on the button 5006, movement of the device toward the user,etc., detected after the press input by contact 5032 on the lock button5006, etc.), the device 100 displays the wind down screen 5013 again. Tosubsequently regain access to the home screen 5029 and/or the musicapplication user interface 5036, the user is required to go through thesequence of steps shown in FIGS. 5D-5F again. In some embodiments, ifthe user, after gaining access to the home screen and/or applicationuser interfaces during the wind down period, does not lock the device100 until the scheduled sleep period is reached, the device transitionsinto sleep mode at the scheduled sleep time and displays a sleep screen(e.g., a darker and simplified wake screen as compared to the wind downscreen) when the user locks and wakes the device again.

FIG. 5J illustrates an exemplary wind down screen 5013 with one or moreselectable options corresponding to preset application functions of oneor more applications. In some embodiments, the user can set up a limitedset of application functions that remains directly accessible on thewind down screen without requiring the user to dismiss the wind downscreen and/or unlock the device to use the application functions. Insome embodiments, as shown in FIG. 5K, an action platter 5047 includingthe one or more selectable options for the application functions isdisplayed on the wind down screen 5013 in addition to other userinterface objects (e.g., time and date element 5012, bedtime reminder5020, dismiss button 5018, affordances 5014 and 5016, etc.) available onthe wind down screen 5013.

In some embodiments, as shown in FIG. 5J, the device 100 displays thewind down screen 5013 that includes a shortcuts affordance 5033. Inresponse to detecting a tap input by a contact 5034 on the shortcutaffordance 5033, the device 100 displays the one or more selectableoptions corresponding to the preset application functions of one or moreapplications (e.g., in a platter that expanded from affordance 5033, adrop down menu, or a pop up window, etc.), as shown in FIG. 5K. In someembodiments, the one or more selectable options corresponding to thepreset application functions, when activated, cause performance of thecorresponding preset application functions. In some embodiments,performance of a preset application function includes displaying anauthentication user interface, and performing the preset applicationfunction after receiving valid authentication information through theauthentication user interface. In some embodiments, the shortcutaffordance 5033 is optionally displayed on the sleep screen and/or goodmorning screen, and optionally displays a different set of applicationfunctions from those shown on the wind down screen. In some embodiments,the wind down screen 5013 that includes the action platter 5047 orshortcut affordance 5033 cannot be dismissed using the regular dismissalgestures (e.g., upward edge swipe input by contact 5024, rightward swipeinput by contact 5022, etc.) to cause navigation to the home screenand/or application user interfaces that are displayed beyond a regularwake screen or lock screen 5025. In some embodiments, a tap hold inputby a contact 5042 on the affordance 5014 causes the flash function to beactivated without unlocking the device, and a tap input by a contact5044 on the affordance 5016 causes the camera function to be activatedwithout unlocking the device. In some embodiments, the affordances 5014and 5016 are not available on the wind down screen 5013.

As shown in FIG. 5K, in response to the tap input by the contact 5034 onthe shortcut affordance 5033, the device 100 displays the action platter5047. The action platter 5047 displays one or more selectable optionscorresponding to preset application functions of one or moreapplications. For example, the action platter 5047 (e.g., expanded orpopped up from shortcuts affordance 5033) displays an alarm option 5054for adjusting a wake alarm set for the current sleep period, a musicoption 5056 for starting playing a preset playlist using a selectedmusic applications (e.g., the music application 480), and a light option5058 for turning on “Calm” lighting using a smart home application. Atap input by a contact 5052 on the alarm option 5054 causes display ofan alarm user interface 9041 (FIG. 9K) from which wake alarm settingsfor the current sleep time period can be adjusted. A tap input bycontact 5050 on the music option 5056 causes playback of the preselectedplaylist to be started using the music application, while the wind downscreen remain displayed and while the display is in the low power ordormant state. In some embodiments, a tap input by a contact 5046outside of the action platter 5047 (FIG. 5K) causes the platter tocollapse and the shortcut affordance 5033 to be displayed again (e.g.,as shown in FIG. 5J). In some embodiments, the options include an optionto launch a preselected application. In response to a tap input on anoption to launch a preselected application, the device 100 displays theapplication (e.g., without requiring the user to navigate passed thewind down screen or regular wake screen in the usual manner describedabove), and allow user to interact with the application in the normalmanner. When the user exits (e.g., navigates away from) the application,the device redisplays the wind down screen 5031.

In some embodiments, an edit button 5052 is included in the actionplatter 5047 (FIG. 5K), and a tap input on the edit button 5052 causesan action or shortcut configuration user interface 5061 (FIG. 5L). Theaction or shortcut configuration user interface 5061 allows a user toconfigure the preset application functions to be included on the winddown screen, and optionally, the sleep screen and/or the good morningscreen. In some embodiments, the shortcut configuration user interface5061 displays currently selected application functions in a firstportion (e.g., under an enabled shortcuts header 5060). The currentlyselected application functions can be removed (e.g., via a minus button5080 displayed for each currently selected application function). Insome embodiments, the shortcut configuration user interface 5061displays a plurality of application categories (e.g., a mindfulnesscategory 5064, a journaling category 5066, etc.), each including one ormore suggested applications (e.g., under the mindfulness category 5064,two applications 5068 and 5070 are displayed). In some embodiments, thedisplayed applications and functions are pre-selected based on thescheduled mode change. For example, the action or shortcut configurationuser interface 5061 displays applications that are preselected inpreparation for bedtime. In some embodiments, one or more applicationfunctions are displayed under each application (e.g., an option 5074 foropening the application, and an option 5076 for starting a sleepmediation function of the application are displayed for the application5068). In some embodiments, a maximum number of functions for a specificapplication is displayed (e.g., to conserve space on the display) andadditional functions can be displayed (e.g., by selected a show moreoption 5078). In some embodiments, the displayed functions are orderedbased on specific criteria (e.g., popularity with respect to one or moreother devices or relevance to a particular condition and/or a useraccount associated with the device 100). In some embodiments, a plusbutton 5082 is displayed next to each application function to add thefunction to the set of currently selected application functions. In someembodiments, the actions available for selection is displayed inresponse to a tap input on an expand affordance displayed next to theapplication (e.g., application 5070).

FIGS. 5M-50 illustrate exemplary user interfaces that correspond to arestricted mode that is displayed during a scheduled mode (e.g., a sleepmode during a sleep period). In some embodiments, during the scheduledmode, the device 100 operates with settings that correspond to (e.g.,designed to promote or enable) a reduced level of user interactions withthe device (e.g., displaying a simplified screen-lock user interface,locking certain user interface features, lowering screen brightness,suppressing notifications, turning on Do-Not-Disturb mode, etc.). Forexample, the device 100 displays a sleep screen 5083 in response to aninput that wakes the display (e.g., a tap input on the touch-screen 112,movement of the device toward the user, etc.), after the device 100 hastransitioned into the sleep mode (e.g., from the wind down mode) at thestart of the scheduled sleep time period (e.g., 10:00 PM). Similar tothe wind down screen 5013, the device 100 does not respond to therightward swipe gesture by a contact 5022 or the upward edge swipegesture by a contact 5024, and does not dismiss the sleep screen 5083.Additionally, the sleep screen 5083 is displayed with a reducedluminosity (e.g., as compared to the wind down screen 5013 and regularwake screen 5025). During the sleep mode, the device 100 is alsooperated with the Do Not Disturb mode activated, as indicated by the DNDindicator 5011 on the sleep screen. In some embodiments, similar to thewind down screen 5013, the sleep screen 5083 is provided with a shortcutbutton 5033 that, when activated by a tap input by a contact 5034,causes display of an action platter with selectable optionscorresponding to a limited set of application functions that arepreselected to be available during the scheduled sleep time period. Insome embodiments, a different set of application functions are madeavailable during the sleep period from those available during the winddown period. In some embodiments, similar to the wind down screen 5013,the sleep screen 5083 requires a predefined input (e.g., a tap input bya contact 5026 on the dismiss button 5018) in order to be dismissed, andonce dismissed, the device navigates to the regular wake screen userinterface 5025 (optionally with a reduced luminosity as well). FIG. 5Nshows the sleep screen 5083 that is displayed when no action ispreselected to be available during the sleep period, and only a wakealarm is set for the sleep period. In FIG. 5N, instead of the shortcutbutton 5033, an alarm indicator 5086 showing the wake time of 6:30 AM isdisplayed. In some embodiments, a tap input on the alarm button 5086,causes display of the alarm user interface 9041 (FIG. 9K) from whichwake alarm settings for the current sleep time period can be adjusted.

FIG. 5O illustrates an exemplary simplified sleep screen 5087 that isdisplayed in place of the sleep screen 5083 or that is displayed duringthe sleep period after a prolonged period of inactivity (e.g., duringactual sleep of the user as detected by the device 100 or a companiondevice such as a watch or other wearable devices) during the scheduledsleep period. In some embodiments, the simplified sleep screen 5087 isfurther dimmed relative to the wind down screen 5013 or sleep screen5083, and has only the current date and no current time and no wake timeindicator displayed. In some embodiments, no shortcut affordance isdisplayed on the simplified sleep screen 5087. In some embodiments, whenthe sleep screen 5087 is displayed during the sleep period in responseto user input waking the device, the device ignores all inputs thatnormally dismisses a regular wake screen or lock screen, and onlydismisses the sleep screen when a predefined input (e.g., a tap input bya contact 5026 on the dismiss button 5018) is detected. In someembodiments, upon dismissing the sleep screen 5087, the device 100displays the regular wake screen 5025. The sleep mode remains activeafter the sleep screen 5087 is dismissed, and the device displays thesleep screen 5087 again whenever the device is woken during the sleepperiod. In some embodiments, a sleep screen that is completely darkexcept for a dim DND indicator is displayed when the device is wokenduring the sleep period. In some embodiments, the sleep screen 5087 doesnot include affordances 5014 and 5016 for triggering the flashlight andcamera functions. In some embodiments, the animated transition betweenthe wind down screen and the sleep screen is triggered when the starttime of the scheduled sleep time period is reached.

FIG. 5P illustrates an exemplary alarm notification screen 5091 that isdisplayed at or proximate to (e.g., slightly delayed after the companiondevice generates the alarm first) the end time of the sleep period(e.g., at 6:30 AM the next day). In some embodiments, the wake alarmuser interface is displayed in conjunction with another non-visual alarmoutput (e.g., a tactile output and/or an audio output). In someembodiments, the alarm notification screen is similar to a wind downscreen, except that the shortcut button or alarm button is replaced witha snooze button 5090. In some embodiments, a tap input by a contact 5088on the snooze button 5090 causes the device 100 to adjust the end timeof the sleep period to a later time (e.g., snooze, temporarily stoppingoutputting the non-visual alarm output). In some embodiments, the alarmnotification screen 5091 also includes the dismiss button 5018 that,when activated by a tap input by a contact 5026, causes the alarmnotification screen 5091 to be dismissed and the non-visual alarm outputto be stopped. The device exits the sleep mode upon dismissing the alarmnotification screen 5091. In some embodiments, upon dismissal of thealarm notification screen 5091, the device displays a good morningscreen 5093, as shown in FIG. 5Q. In some embodiments, if a wind upperiod after a sleep period is not enabled, the device displays theregular wake screen 5025 instead of a good morning screen. In someembodiments, the normal inputs that dismisses a regular wake screen orlock screen (e.g., upward edge swipe input by a contact 5024, arightward swipe input by a contact 5022) does not dismiss the alarmnotification screen 5091.

In some embodiments, a good morning screen 5093 is displayed in responseto a user input that wakes the device from a low power or dormant stateduring a preset wind up period (also referred to as a good morningperiod) succeeding the recently completed sleep period. During the windup period, the Do Not Disturb mode is still turned on, and mostnotifications are still suppressed. Scheduled alarms are not suppressedduring the good morning period, the sleep period, the wind down period,or any combination thereof. In some embodiments, the good morning screen5093 displays the date and time element 5012, a good morning message,and has a brighter screen luminosity as compared to the sleep screen andthe wind down screen. In some embodiments, the good morning screen 5093displays some low impact information such as the weather in anotification or platter 5022. In some embodiments, the normal inputsthat dismisses a regular wake screen or lock screen (e.g., upward edgeswipe input by a contact 5024, a rightward swipe input by a contact5022) does not dismiss the good morning screen 5093. In someembodiments, the good morning screen 5093 also includes the dismissbutton 5018 that, when activated by a tap input by a contact 5026,causes the good morning screen 5093 to be dismissed. The device exitsthe wind up mode upon dismissing the good morning screen 5093. In someembodiments, upon dismissal of the good morning screen 5093, the devicedisplays the regular wake screen 5025, as shown in FIG. 5R. In someembodiments, as shown in FIG. 5R, notifications that were received andsuppressed during the wind down period, the sleep period, the wind upperiod, or any combination thereof (e.g., a missed messages notification5094, a missed calls notification 5096, etc.) are displayed on the wakescreen user interface 5025. In some embodiments, upon becomingavailable, a notification 5098 regarding the sleep quality of therecently completed sleep period is displayed. In some embodiments, thedevice only displays the notification 5098 when the user has adhered tothe sleep schedule (e.g., did not skip wind down, did not wake orinteract with the device during the sleep period, etc.). In someembodiments, a tap input by a contact 5100 on the notification 5098causes the device to display a user interface 5101 of an applicationthat manages the sleep schedule. In some embodiments, the regular wakescreen 5025 shown in FIG. 5R is dismissed by a regular input used todismiss a regular wake screen user interface (e.g., an upward swipegesture by a contact 5024, optionally combined with authenticationinputs, etc.). Upon dismissal of the regular wake screen user interface5025, the home screen user interface 5029 is displayed, as shown in FIG.5S.

FIG. 5T illustrates an exemplary sleep data user interface 5101 inaccordance with some embodiments. The sleep data user interface 5101optionally includes a weather section 5102 showing the weather forecastfor the day, a summary 5104 of the recently completed sleep period,sleep quality data 5106 showing the quality of sleep monitored by theelectronic device or a companion device of the electronic device, weeklysummary data 5108 that shows the sleep data for a sequence of multipledays (e.g., showing whether the user has consistently missed or met thesleep goal, or adhered to the sleep schedule for a number of days), anda sleep tips section 5110 offering additional information about how theuser's sleep quality can be improved. In some embodiments, the sleepdata user interface 5101 includes additional or fewer sections thanthose shown in FIG. 5T. In some embodiments, the sleep data userinterface 5101 displays data for a period different from a week. In someembodiments, the sleep data user interface 5101 displays positivecoaching messages (e.g., does not display summary of the sleep period ifthe user does not meet his/her established sleep goal).

FIGS. 5U-5V illustrate displaying a regular wake screen 5025 in responseto various wake inputs while the current time is outside of the presettime period preceding and/or after the scheduled mode change (thecurrent time (e.g., 6:29 PM on Tuesday, 6:40 PM on Tuesday, etc.) isoutside of the wind down period and the good morning period, and alsooutside of the sleep period). For example, as shown in FIGS. 5U1-5U4, incontrast to the scenario shown in FIGS. 5A1-5A4, the device displays aregular wake screen 5025 in response to the user raising the devicetoward the user when the current time is 6:29 PM on Tuesday. In FIGS.5V1-5V2, in response to arrival of a new notification, the devicedisplays a regular wake screen 5025 with the new notifications 5112 andan unread notification 5114 received earlier when the current time is6:29 PM on Tuesday. In FIGS. 5W1-5W2, in response to a tap input by acontact 5010 or a press input by a contact 5008 on the lock button 5006,the device displays the wake screen user interface 5025 that optionallyincludes missed notifications 5112 and 5114, when the current time is6:40 PM on Tuesday.

FIGS. 5X-5AB shows various user interfaces that are accessible inresponse to dismissal gestures on the regular wake screen user interface5025 when the current time (e.g., 6:45 PM on Tuesday) is outside of thewind down period, the wind up period and the sleep period, in accordancewith some embodiments. For example, in response to an upward edge swipeby a contact 5024, the device 100 displays an authentication userinterface 5027 (FIG. 5Y). Upon entry of authentication input by acontact 5030 (FIG. 5Y), the device displays the home screen userinterface 5029 (FIG. 5Z). In some embodiments, if authentication inputhas been obtained without active user input (e.g., through facialrecognition or retina scanner, etc.), the device displays the homescreen user interface 5029 or a last displayed application userinterface directly upon dismissal of the regular wake screen 5025. Insome embodiments, in response to a rightward swipe input by a contact5022 detected on the regular wake screen 5025 (FIG. 5X), the devicenavigates to the widget screen 5117 that includes a listing of widgetscorresponding to different applications (e.g., widget 5118 for themessages application, widget 5120 for the calendar application, widget5122 for the calendar application, etc.), as shown in FIG. 5AA. In someembodiments, the widget screen 5117 is not displayed in response to therightward swipe if detected on a wind down screen, a sleep screen, or agood morning screen. In some embodiments, additional widgets can beadded to the widget user interface 5117 (e.g., via an edit button 5124).In some embodiments, in response to a downward edge swipe input by acontact 5116 detected on the upper right corner of the regular wakescreen 5025 (FIG. 5X), the device displays a control panel 5126 thatincludes selectable options for triggering a plurality of device controlfunctions (e.g., options for adjusting display brightness, adjustingdevice volume, starting AV output, locking screen orientation, turningon/off network connections, turning on/off airplane mode, turning on/offBluetooth connection, etc.) and optionally some application functions(e.g., starting media playback, turning on flashlight, turning oncamera, display alarm application, display a calculator application,etc.), as shown in FIG. 5AB. In some embodiments, the control panel 5126includes an affordance 5130 for activating the wind down mode or thesleep mode before their scheduled start times.

FIGS. 5AB-5AC illustrate that a user input by a contact 5128 is detectedon the affordance 5130, when the current time (e.g., 6:45 PM on Tuesday)is outside of the wind down period, the sleep period, and the goodmorning period. In response to the user input activating the affordance5130, the device starts the wind down mode immediately, irrespective ofthe bedtime being set for 10:00 PM and before the scheduled start timeof the wind down period (e.g., 9 PM). In some embodiments, asillustrated in FIG. 5AB, a wind down period can be started using theaffordance 5130 when no wind down period is scheduled before theupcoming sleep period. In some embodiments, once the wind down period isstarted, it is extended until the scheduled sleep period is started. Insome embodiments, the affordance 5130 is optionally used to start thesleep period as well or instead (e.g., once wind down period has alreadybeen started (e.g., according to schedule or started manually)).Allowing the wind down mode to be started manually before scheduled timeallows the user to take advantage of certain features of the modechange, such as the settings designed to promote a reduced level of userinteraction, dimmed display, and Do-Not-Disturb mode, before thescheduled mode change.

FIG. 5AC illustrates an exemplary wind down screen (e.g., wind downscreen 5013) that is displayed in response to manual request using thecontrol panel affordance 5130. After the wind down mode is activatedmanually, the wind down screen is displayed in response to user inputthat wakes the device during the wind down mode until the scheduledbedtime is reached. In some embodiments, a separate affordance isdisplayed in the control panel 5126 for activating the sleep mode aheadof the scheduled sleep time period, and in response to activation of theaffordance, the device enters the sleep mode directly, optionallyskipping any scheduled wind down period or terminating the wind downperiod before its scheduled end time, and displays the sleep screen 5083right away. After the sleep mode is activated manually, the sleep screen5083 is displayed (FIG. 5AD) in response to user input that wakes thedevice during the sleep mode until the scheduled wake time is reached.As shown in FIG. 5AD, the device 100 displays the sleep screen 5083 witha wake alarm indicator 5086 and a dismiss button 5018. In someembodiments, after a wind down mode or sleep mode has been started, theuser can manually terminate the wind down mode or sleep mode by usingthe control panel affordance 5030 as well (e.g., toggling the state ofthe affordance 5030). In some embodiments, the control panel 5126 isaccessible by dismissing the wind down screen 5013 or the sleep screen5083 using the dismiss button 5018, and swipe down from the upper rightcorner of the display when the wake screen 5025 is displayed (e.g., asdescribed in FIGS. 5X and 5AB). If a user is awake past bedtime andwould like to exit an active wind down mode or sleep mode, the user canterminate the wind down mode and/or sleep mode manually using theaffordance 5030 in the control panel 5126. In some embodiments, if theuser wishes to reset the start time of the wind down or sleep mode to alater time after the wind down or sleep mode has been activated, theuser can access the bedtime configuration user interface using the alarmindicator 5084 on the wind down screen or the alarm indicator 5086 onthe sleep screen 5083, to reset the bedtime for the current sleepperiod.

FIG. 5AE illustrates an exemplary notification 5132 that alerts the userthat the wind down mode is about to be started. The notification 5132 isoptionally displayed a preset time period (e.g., 5 minutes, 10 minutes,etc.) before the scheduled start time of the wind down period. In someembodiments, the notification 5132 is overlaid on a regular wake screenuser interface 5025, as shown in FIG. 5AE. In some embodiments, thenotification 5132 includes a visual indication that the wind down periodwill begin shortly (e.g., in 5 minutes), and provides an option to delaythe start of the scheduled wind down period (e.g., a delay button 5134,that when activated, delays the start of the wind down period by apreset amount of time (e.g., 30 minutes), and a skip button 5136, thatwhen activated, skips the scheduled wind down period, and either (1)starts the sleep mode immediately or (2) skips the scheduled wind downperiod for the day and starts the sleep mode at the designated time). Insome embodiments, the wind down delay time is configurable, and the usercan select various amounts of time to delay the wind down period in theconfiguration user interface for the sleep schedule.

FIGS. 6A-6D are flowchart diagrams of a method 6000 of providingenhanced access restriction during a preset time period before and/orafter a scheduled mode change, in accordance with some embodiments.

According to method 6000, in response to an input to wake a computersystem from a low power state, the computer system automatically selectsbetween a regular user interface that corresponds to a restricted stateof the computer system (e.g., a regular wake screen or lock screen) anda special user interface that corresponds to the restricted state of thecomputer system (e.g., a wind down screen, or a good morning screen)based on a comparison of the current time with a preset time periodpreceding or succeeding a scheduled mode change (e.g., a sleep mode). Inparticular, the computer system displays the special user interface thatcorresponds to the restricted state of the computer system when thecurrent time is within the preset time period preceding or succeedingthe scheduled mode change, and displays the regular user interface thatcorresponds to the restricted state of the computer system when thecurrent time is outside of the preset time period. The special userinterface that corresponds to the restricted scheduled mode changerequires a special input to be detected in order to be dismissed, andupon dismissal of the special user interface, the computer systemnavigates to the regular user interface that corresponds to therestricted state. Automatically displaying a user interface thatcorresponds to a restricted state of the computer system based on acomparison of current time with a preset time period will perform anoperation when a set of conditions has been met without requiringfurther user input. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently. In particular, automaticallydisplaying a wind down screen in response to wake input while thecurrent time is within a preset time period before or after a sleepperiod of an active sleep schedule, promotes a reduction of interactionwith the computer system and distraction caused by the computer systemprior to the scheduled bedtime, and helps the user to have betterquality of sleep during the sleep period. This method is illustrated inFIGS. 5A1-5G and 5J, 5Q, and 5U1-5Z, for example, where the wind downscreen 5013 and the good morning screen 5093 cannot be dismissed using aregular dismissal gesture for dismissing a regular wake screen 5025, andrequires a tap gesture on the dismiss button 5018 to navigate to theregular wake screen 5025, and from the regular wake screen 5025, theuser can gain access to other user interfaces of the computer systemusing various gestures.

The method 6000 is performed at a computer system (e.g., a handheldelectronic device, a mobile phone, a tablet device, a computer, etc.) incommunication with a display generation component (e.g., a display, atouch-screen display, a projector, a head-mounted display (HMD), etc.)and one or more input devices (e.g., a touch-sensitive surface (e.g.,separate from a display or integrated in a touch-screen display), anaccelerometer, a camera, a motion sensor, etc.). In the method 6000, thecomputer system displays (6002) (e.g., in response to a respectivereceived input and/or detected event (e.g., locking the device,receiving a notification when in a low power mode (e.g., display-offstate, dimmed always-on state, etc.), tapping or raising the displaygeneration component when in the low power mode, etc.) that correspondsto a request for entering a restricted state of the computer system(e.g. a request for displaying a respective screen-lock user interface(e.g., a lock screen, a wake screen in either the locked state or theunlocked state, a coversheet user interface, etc.)), via the displaygeneration component, a respective user interface (e.g., selectivelydisplaying a first user interface or a second user interface) thatcorresponds to a restricted state (e.g., a screen-restricted state(e.g., in the restricted state, interaction with graphical userinterfaces of the computer system is restricted or blocked by a lockscreen, a wake screen in the authenticated state and/or theunauthenticated state, a coversheet user interface, etc.)) of thecomputer system. For example, the respective user interface is displayedas an initial user interface that is when the display generationcomponent transitions from an off state, low-power always-on state,and/or dormant state (e.g., completely dark or dimmed always-on state)to a normal display-on state (e.g., a regular wake screen userinterface, with device-unlocking authentication already performed, orwith device-unlocking authentication not yet performed), the respectiveuser interface is optionally a user interface that is displayedimmediately after the user locks the device (e.g., by pressing on thelock button or power button of the device), and/or the respective userinterface is optionally a system-level coversheet user interface that isdisplayed to cover any currently displayed user interface includingapplication user interfaces and home screens in response to a predefinedinput, etc.). To display the respective user interface includes: thecomputer system, in accordance with a determination that a current time(e.g., a time at which the first input was detected, a time that thedisplay is turned on in response to the first input, etc.) is outside of(e.g., before the start time of) a first preset time period (e.g., anextended time period (e.g., not a single point in time, but a period oftime with distinct start and end time points), such as a wind downperiod (e.g., 1 hour, 45 minutes, etc.), a wind up period (e.g., 1 hour,30 minutes, etc.), etc.) preceding or following (e.g., adjacent to,immediately before (e.g., having an end time that is the same as orimmediately before a start time of a respective scheduled time period),immediately after (e.g., having a start time that is the same as orimmediately after an end time of a respective scheduled time period),etc.) a scheduled mode change for the computer system (e.g., thescheduled mode change includes entering and remaining in a firstscheduled time period (e.g., a first sleep schedule with scheduled startand end times, a first DND time period with scheduled start and endtimes, etc.) in which the computer system and/or the display generationcomponent are operating with special settings (e.g., special screen lockfeatures, darkened/reduced luminance for the display, and/or Do NotDisturb mode being turned on, etc.)), displays (6004) a first userinterface (e.g., a regular screen-lock user interface, such as a wakescreen that is different from a home screen that includes applicationicons for launching respective applications, the regular wake screen isdisplayed when the device switches from a low-power state to a normaldisplay-on state outside of a wind down period before a start time of asleep schedule or DND schedule, the same wake screen user interface isoptionally displayed immediately after the user locks the device, and/orwhen the user provides a required input to cover the screen with thescreen-lock user interface, etc.) that corresponds to the restrictedstate of the computer system; and in accordance with a determinationthat the current time is within the first preset time period (e.g., winddown period (e.g., 1 hour, 45 minutes, etc.), a wind up period (e.g., 1hour, 30 minutes, etc.), etc.) preceding or following the scheduled modechange (e.g., the scheduled mode change includes entering and remainingin the first scheduled time period in which the computer system and/orthe display generation component are operating with special settings(e.g., to promote better sleep, less distractions, etc.)), displays(6006) a second user interface (e.g., a wind down user interface that isdisplayed within a preset period of time before the sleep period isstarted, a wind up user interface that is displayed within a presetperiod of time after the sleep period ends, etc.) that corresponds tothe restricted state (e.g., screen-locked state, screen-restrictedstate) of the computer system, the second user interface being differentfrom the first user interface (e.g., the second user interface beingdifferent from the first user interface in appearance (e.g., with lessluminosity, different background, different color scheme, etc.),includes different sets of user interface objects (e.g., missing someuser interface objects, and adding some other user interface objects),and/or enabling different sets of user inputs and/or functions, etc.).While displaying the respective user interface (e.g., the selectivelydisplayed first user interface or second user interface) thatcorresponds to the restricted state of the computer system, the computersystem detects (6008) a first input directed to the respective userinterface (e.g., a touch input on the touch screen display that displaysthe respective user interface, an in-air tap gesture detected while agaze input is directed to the respective user interface, a swipe left, awipe right, etc.). In response to detecting the first input directed tothe respective user interface (6010): in accordance with a determinationthat the first input meets first criteria (e.g., criteria for dismissinga regular screen-lock user interface (e.g., a regular wake screen,coversheet user interface, lock-screen user interface, etc.), criteriafor unlocking the device to display a home screen, a defaultapplication, or a last displayed application, etc.), and that the firstuser interface (e.g., the regular screen-lock user interface) wasdisplayed when the first input was detected (e.g., the respective userinterface is the first user interface because the current time wasoutside of the first preset time period), the computer system replaces(6012) display of the first user interface with a third user interfacethat is different from the first user interface and the second userinterface (e.g., the third user interface is a user interface that isimmediately displayed when the computer system exits the restrictedstate (e.g., a home screen user interface, or a last displayed userinterface of an application prior to the display generation componentgoing into the off, low-power, or dormant state and/or a locked state);and in accordance with a determination that the first input meets secondcriteria different from the first criteria (e.g., criteria totemporarily dismiss the second user interface to allow access to theuser interfaces of the computer system in a manner that is availablewhen the restricted mode is displayed with the first user interface,without exiting the restricted mode (e.g., without displaying the homescreen or application user interfaces)) (e.g., the second inputactivates the “dismiss” button on the second user interface, the secondinput follows a predefined path on the touch-sensitive surface, etc.),and that second user interface was displayed when the first input wasdetected (e.g., the respective user interface is the second userinterface because the current time was within the first preset timeperiod), the computer system replaces (6014) display of the second userinterface (e.g., wind down wake screen, wind up wake screen, etc.) withdisplay of the first user interface (e.g., the regular screen-lock userinterface). In some embodiments, the computer system remains in therestricted state but dismisses the second user interface so that theuser can gain access to other user interfaces (e.g., home screen andapplication user interfaces) of the computer system starting from thefirst user interface (e.g., the regular wake user interface (e.g., ineither the authenticated mode (e.g., authentication data has beenreceived and verified) or the unauthenticated mode (e.g., authenticationdata has not yet been received or verified)), the lock screen userinterface, etc.). In some embodiments, after the computer systemdismisses the first user interface (e.g., in response to a second userinput that meets the first criteria) and displays the home screen or anapplication user interface, when the restriction state is displayedagain in response to user inputs (e.g., as a coversheet) before thecomputer system is locked, it is displayed with the first user interfacerather than the second user interface, so an input meeting the firstcriteria can be used to gain access to the home screen and applicationsof the computer system. If a request for displaying a respective userinterface corresponding to the restricted mode is received again afterthe computer system is locked, the restricted state is displayed withthe second user interface again and the computer system only grantsaccess to the home screen and applications when an input meeting thesecond criteria followed by an input meeting the first criteria arereceived. In some embodiments, the scheduled mode change is an operationmode of the computer system used during a sleep period of apreconfigured sleep schedule, and the first preset time period is apreconfigured wind down period that precedes a scheduled sleep period.In some embodiments, a preset time (e.g., 1 minute, 5 minutes, etc.)before the start time of the wind down period, the computer systemdisplays an alert that notifies the user that the wind down period isabout to start, and provides an interface for the user to input aninstruction to delay the start of the wind down period (e.g., delay by10 minutes, 20 minutes, etc.), or skip the wind down period entirely(e.g., to start the sleep mode right away). In some embodiments, thefirst user interface displays the current time, and the second userinterface displays both the current time and the starting time of thescheduled mode change (e.g., the start time of the scheduled bedtime).In some embodiments, the starting time of the first preset time periodis preset by the user during a configuration process (e.g., setting upthe bedtime schedule and bedtime modes). In some embodiments, the presetstart time of the first preset time period is overridden in response toactivation of a first preset control center affordance (e.g., a bed iconwith a first appearance) before the preset start time is reached, andthe computer system starts the first preset time period and associatedspecial mode (e.g., wind down mode) right away. In some embodiments, thepreset start time of the scheduled mode change is overridden in responseto activation of a second preset control center affordance (e.g., a bedicon with a second appearance) before the preset start time is reached,and the computer system starts the scheduled mode change (e.g., sleepmode) right away (e.g., skipping wind down). In some embodiments, ananimated transition from the first user interface to the second userinterface is displayed when the current time reaches the start time ofthe preset first time period preceding the scheduled mode change (e.g.,the regular wake screen or lock screen is transformed into the wind downscreen when the start time of the wind down mode is reached). In someembodiments, an animated transition from the second user interface to auser interface corresponding to the restricted mode during the schedulemode change (e.g., the sleep screen) is displayed when the current timereaches the start time of the scheduled mode change (e.g., the wind downscreen is transformed into the sleep screen when the start time of thesleep mode is reached).

In some embodiments, in response to detecting the first input that isdirected to the respective user interface: in accordance with adetermination that the first input meets the first criteria and does notmeet second criteria different from the first criteria (e.g., the firstinput meets the criteria for dismissing the regular screen-lock userinterface, but not the criteria for dismissing the special wind downwake screen, or wind up wake screen), and that the second user interfacewas displayed when the first input was detected (e.g., the respectiveuser interface is the second user interface because the current time waswithin the first preset time period), the computer system forgoes (6016)replacing display of the second user interface with the third userinterface (e.g., the regular gesture for dismissing the regular wakescreen does not dismiss the second user interface (e.g., the wind downuser interface, the wind up user interface, etc.)). In some embodiments,the computer system also forgoes replacing display of the second userinterface with the first user interface when the first input meets thefirst criteria and does not meet the second criteria. The first inputthat meets the first criteria but not the second criteria is ignored bythe computer system when it is detected at a time that the second userinterface is being displayed. In some embodiments, the first userinterface (e.g., the regular wake screen or lock screen) are providedwith an adjacent user interface such as a widget user interface thatdisplays widgets corresponding to different applications, and the widgetscreen is displayed with in response to a leftward swipe or rightwardswipe; but such widget user interface is not displayed in response to aleftward swipe or rightward swipe if the second user interface isdisplayed instead of the first user interface. This is illustrated inFIGS. 5C-5E, for example, where in response to detecting the first input(e.g., the swipe right gesture 5022 or the swipe up gesture 5024 in FIG.5C), the computer system (e.g., the portable multifunction device 100)displays the second user interface (e.g., the wind down screen 5013 inFIG. 5C) and forgoes replacing display of (e.g., maintains display ofthe wind down screen 5013 in FIG. 5D) the second user interface with thethird user interface (e.g., wake screen user interface 5025 in FIG. 5E).Forgoing replacing the display of the second user interface with thethird user interface, when the second user interface was displayed andthe first input meets the first criteria but not the second criteria,performs an operation (e.g., maintaining the second user interfacedespite the first input) when a set of conditions has been met (e.g.,the first input meets the first criteria but not the second criteria)without requiring further user input. Performing an operation when a setof conditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, after replacing display of the second userinterface with display of the first user interface (e.g., in response todetecting the input that meets the second criteria), the computer systemdetects (6018) a second input directed to the first user interface. Inresponse to detecting the second input directed to the first userinterface, in accordance with a determination that the second inputmeets the first criteria, the computer system replaces display of thefirst user interface with the third user interface (e.g., the third userinterface is a home screen user interface, or a last displayed userinterface of an application prior to the display generation componentgoing into the display-off state and/or a locked state). In someembodiments, the restricted state of the computer system preventsdisplay of and/or access to the home screen and application userinterfaces with the display of a respective screen-lock user interface(e.g., a regular wake screen, a lock screen, a special wake screen, aspecial lock screen, etc.). In some embodiments, the screen-lock userinterface is an initial user interface that is displayed in response toan input (e.g., user movement raising the computer system relative tothe physical environment, a touch input on a touch-sensitive surface,activation of the screen ON/OFF button, etc.) or event (e.g., arrival ofa notification, generation of an alert, etc.) that occurred while thedisplay generation component was in a low-power state (e.g., adisplay-off state or a dimmed always-on state (e.g., the display iscompletely dark and dormant or has reduced function and/or luminance,due to prolonged absence of user inputs, previous activation of a screenON/OFF button, etc.)). In response to the input or event, the computersystem causes the display generation component to transition from thelow-power state to a normal display-on state (e.g., switching thetouch-screen display from the display-off state to a normal display-onstate, or from the dimmed always on state to a normal display-on state,etc.); and selectively displays the first user interface or the seconduser interface in accordance with whether the current time is within oroutside of the first preset time period (e.g., wind down period (e.g., 1hour, 45 minutes, etc.), a wind up period (e.g., 1 hour, 30 minutes,etc.), etc.) preceding or following a scheduled mode change (e.g., thefirst scheduled time period). In some embodiments, the screen-lock userinterface is a user interface that is immediately displayed when a userinput that locks the computer system (e.g., a press input on a powerbutton or lock button on the computer system) is detected. In someembodiments, the screen-lock user interface is a user interface that isa system user interface that covers any currently displayed applicationuser interface or home screen in response to a predefined user input(e.g., a downward swipe from the top of the display, etc.). In someembodiments, the screen-lock user interface is an authentication screenthat requires input of authentication information to unlock the computersystem. In some embodiments, the screen-lock user interface is a userinterface that can be persistently displayed in either an authenticatedstate or an unauthenticated state depending on whether theauthentication information has already been obtained (e.g., previouslyvia an authentication screen, or via other input authenticationmechanisms (e.g., facial recognition, fingerprint recognition, passcodeentry, password gesture entry, etc.)). This is shown in FIGS. 5D-5E, forexample, where the portable multifunction device 100 detects the userinput 5026 on the dismiss button 5018, and in response, replaces displayof the wind down screen 5013 with the regular wake screen 5025. Afterreplacing the second user interface with the first user interface,further replacing the first user interface with the third userinterface, in response to detecting that the second input directed tothe first user interface satisfies first criteria, performs an operation(e.g., replacing the first user interface with the third user interface)when a set of conditions has been met (e.g., the second input satisfiesthe first criteria) without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the scheduled mode change starts (6020) at a firstscheduled start time and ends at a first scheduled end time that isdifferent from the first scheduled start time, and during the scheduledmode change, the computer system operates with settings that correspondto (e.g., designed to promote or enable) a reduced level of userinteractions with the computer system (e.g., displaying a simplifiedscreen-lock user interface, locking certain user interface features,lowering screen brightness, suppressing notifications, turning onDo-Not-Disturb mode, etc.). This is illustrated in FIG. 5O, for example,where during the scheduled mode change (e.g., sleep mode), the computingdevice (e.g., the portable multifunction device 100) operates withsettings that correspond to a reduced level of user interactions withthe computer system (e.g., the simplified sleep screen 5087, which has alower screen brightness and does not display the time). Operating thecomputing device with settings that correspond to a reduced level ofuser interactions with the computer system during the scheduled modechange performs an operation (e.g., activating the settings thatcorresponds to the reduced level of user interactions) when a set ofconditions (e.g., during the scheduled mode change) has been met withoutrequiring further user input. Performing an operation when a set ofconditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the second user interface includes (6022) one ormore selectable options corresponding to preset application functions ofone or more applications, wherein activation of a respective selectableoption corresponding to a first preset application function of thepreset application functions of the one or more applications causesperformance of the first preset application function. In someembodiments, the second user interface is a wind down screen thatincludes user interface affordances that correspond to a set of presetapplication functions, including performing a preset operation of anapplication without breaking through the wind down screen or launchingthe application, or breaking through the wind down screen and launchingthe application, etc. In some embodiments, if an application orapplication operation is included in the set of actions displayed on thesecond user interface (e.g., through a pre-configuration processassociated with the second user interface or the first preset timeperiod), the application or application function is accessible withinthe first preset time period preceding or following the scheduled modechange period. In some embodiments, if an application or applicationoperation is not included in the set of actions displayed on the seconduser interface, the computer system prevents access to the applicationor application operation unless the user provides the required inputs todismiss the second user interface and the first user interface to gainaccess to the home screen. In some embodiments, the second userinterface includes multiple selectable options that correspond todifferent application operations of the same application. For example,in some embodiments, the second user interface displays a firstselectable option that corresponds to a playback function of a mediaplayback application for playing a selected playlist, a secondselectable option that corresponds to switching an output device for themedia playback application from speaker to headphone, and a third optionthat corresponds to breaking through the screen-lock user interface andlaunching the media player application. This is illustrated in FIG. 5K,for example, where the second user interface (e.g., the wind down screen5013) includes one or more selectable options (e.g., the alarm option5054, the music option 5056, and the light option 5058) corresponding topreset application functions of one or more applications (e.g., playinga specific playlist in a music application). Causing the performance ofthe first preset application function in response to the activation of arespective selectable option reduces the number of inputs needed toperform an operation. Reducing the number of inputs needed to perform anoperation enhances the operability of the device, and makes theuser-device interface more efficient, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

In some embodiments, the second user interface includes (6024) aselectable user interface object that, when activated, causes display ofan editing user interface that includes selectable options forconfiguring the preset application functions to be included on thesecond user interface. In some embodiments, the action platter thatincludes the user interface affordances of the preset applicationfunctions available on the wind down screen, sleep screen, and/or windup screen also includes an “edit” button. The edit button, whenactivated by a tap input, causes an editing user interface to bedisplayed (e.g., overlaying or temporarily replacing display of the winddown screen, sleep screen, and/or wind up screen). The editing userinterface optionally is the same user interface that is displayed duringthe on-boarding process where the user set up the wind down, bedtime,and wind up modes. In some embodiments, the editing user interfacedisplays the currently included application functions (e.g., performinga preset application operation of a selected application, launching aselected application, etc.), and a listing of other availableapplications and/or application operations for the availableapplications. In some embodiments, the editing user interface lists theavailable applications in groupings that correspond to the categories ofthe applications (e.g., a grouping for music, a grouping for roomcomfort, a grouping for journaling, etc.). In some embodiments, undereach application, a limited set of application functions are provided,including a first application operation, a second application operation,and an operation for launching the application. In some embodiments,under some applications, only an option for launching the application isavailable for selection. In some embodiments, under some applications,only options for application operations are available, and theapplication cannot be launched from the action platter shown on thesecond user interface. In some embodiments, the application operationsand/or available applications provided in the editing user interfaceinclude application operations and/or applications that areintelligently recommended by the computer system based on available userdata (e.g., demographic data, usage history data, etc.) and/orstatistical data of average users. This is illustrated in FIGS. 5K-5L,for example, where the second user interface (e.g., the wind down screen5013) includes a selectable user interface object (e.g., the edit button5052) that, when activated, causes display of an editing user interface(e.g., the shortcut configuration user interface 5061) that includesselectable options for configuring the preset application functions tobe included on the second user interface (e.g., the option 5074, whichcan be included via the plus button 5082). Causing the display of anediting user interface that includes selectable options for configuringthe preset application functions to be included on the second userinterface, in response to activating a selectable user interface object,reduces the number of inputs needed to perform an operation (e.g.,displaying an editing user interface). Reducing the number of inputsneeded to perform an operation enhances the operability of the device,and makes the user-device interface more efficient, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, wherein the one or more selectable optionscorresponding to preset application functions of one or moreapplications include (6026): a first selectable option corresponding toa first preset application function of a first application, wherein thefirst selectable option, when selected, causes the computer system todisplay the first application (e.g., breaking through the second userinterface, and replacing display of the second user interface withdisplay of a user interface of the first application); and a secondselectable option corresponding to a second preset application functionof a second application (e.g., the same as the first application, ordifferent from the first application), wherein the second selectableoption, when selected, causes the computer system to perform a presetoperation of the second application (e.g., to execute a task usingfunctionality of the second application, without breaking through thesecond user interface or replacing display of the second user interfacewith display of a user interface of the second application). This isillustrated in FIG. 5L, for example, where the one or more selectableoptions (e.g., the option 5074 and 5076) include a first selectableoption causing display of the first application (e.g., “Open App” option5074) and a second selectable option causing the computer system toperform a preset operation of the second application (e.g., “Start SleepMeditation” option 5076). Displaying different selectable optionscorresponding to different preset application functions of differentapplications reduces the number of inputs needed to perform an operation(e.g., activating a respective application function). Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device, and makes the user-device interface more efficient,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination the current timeis within the first preset time period of the scheduled mode change, thecomputer system operates (6028) the computer system with an activatedDo-Not-Disturb mode of the computer system (e.g., forgoing providing atleast some of the notifications and alerts at the computer system). Insome embodiments, the DND mode is automatically activated by thecomputer system in response to the current time reaching the start timeof the first preset time period preceding the scheduled mode change, andthe DND mode persists through the first preset time period and thescheduled mode change, and optionally persists through another presettime period immediately succeeding the scheduled mode change, unless theDND mode or the scheduled mode change is skipped or terminated beforethe scheduled end time of the scheduled mode change. This is illustratedin FIGS. 5M-50, for example, where the computer system (e.g., theportable multifunction device 100) is operated with an activatedDo-Not-Disturb mode of the computer system (e.g., as represented by theDND indicator 5011). Operating the computer system with an activatedDo-Not-Disturb mode of the computer system in accordance with adetermination the current time is within the first preset time period ofthe scheduled mode change performs an operation when a set of conditionshas been met without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, after replacing the second user interface with thethird user interface, the computer system detects (6030) that thecomputer system has reentered the restricted state of the computersystem (e.g., after going from wind down to home screen UI, screen islocked again). After the computer system has reentered the restrictedstate of the computer system and while the computer system is in therestricted state, the computer system receives a third input (e.g., aninput to wake the display generation component of the computer system).In response to receiving the third input, in accordance with adetermination that the current time is within the first preset timeperiod, the computer system redisplays the second user interface (e.g.,wind down wake screen). In some embodiments, in response to detectingthe third input, in accordance with a determination that the currenttime is within the scheduled mode change, the computer system displaysthe screen-lock user interface that corresponds to the scheduled modechange (e.g., the sleep screen for the sleep mode). In some embodiments,after the computer system has dismissed the second user interface or thescreen-lock user interface that corresponds to the scheduled modechange, the computer system maintains the special operation mode (e.g.,wind down mode, sleep mode, DND mode, etc.) while the user interactswith the computer system. After the device is locked again, the specialscreen lock user interface that corresponds to the special operationmode is redisplayed and the user has to provide the predefined inputagain to get to the regular wake screen. This is illustrated in FIGS.5E-5I, for example, where after replacing the second user interface(e.g., the regular wake screen 5025) with third user interface (e.g.,the home screen user interface 5029), the computer system (e.g., theportable multifunction device 100) reenters the restricted state of thecomputer system (e.g., is locked again via the button 5006 in FIG. 5H)and in accordance with a determination that the current time is withinthe first preset time period (e.g., the wind down period), the computersystem redisplays the second user interface (e.g., the wind down screen5013 in FIG. 5I). Redisplaying the second user interface, in response toreceiving the third input and in accordance with a determination thatthe current time is within the first preset time period, performs anoperation when a set of conditions has been met without requiringfurther user input. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the first preset time period preceding or followingthe scheduled mode change has (6032) a duration that is preselected by auser (e.g., during a configuration process that sets up the sleepschedule). In some embodiments, the scheduled mode change does not needto be preceded by the first scheduled time period if the user does notenable the first scheduled time period preceding the scheduled modechange (e.g., when the user sets a duration of zero for the first presettime period preceding the scheduled mode change (e.g., the wind downperiod), or does not enable the wind down mode preceding the sleepmode). This is shown in FIGS. 9X-9Y, for example, where the first presettime period preceding or following the scheduled mode change (e.g., thewind down period) has a duration that is preselected by a user (e.g.,via the wind down period selector 9140, the minus button 9142, and theplus button 9144 for the peripheral device 700 in FIG. 9X, via the winddown setup user interface 9158 for the portable multifunction device100). Allowing the user to preselect the duration of the first timeperiod preceding or following the scheduled mode change performs anoperation (e.g., displaying a respective user interface) when a set ofconditions has been met (e.g., based on a comparison of current time andthe scheduled mode change) without requiring further user input.Performing an operation when a set of conditions has been met withoutrequiring further user input controls enhances the operability of thedevice, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the second user interface includes (6034) aselectable option that corresponds to an alarm for an end time of thescheduled mode change (e.g., the selectable option is an alarm icon withtext indicating the wake alarm time for the end of the sleep mode). Inthe method 6000, the computer system detects a fourth input that isdirected to the selectable option that corresponds to the alarm for theend time of the scheduled mode change (e.g., detecting a tap input onthe alarm icon included on the wind down screen, e.g., inside the actionplatter shown on the wind down screen). In response to detecting thefourth input, the computer system displays a fourth user interface thatincludes user selectable options for modifying one or more aspects of anupcoming occurrence of the scheduled mode change (e.g., options forcanceling the alarm and/or modifying the end time of the scheduled modechange for an upcoming occurrence of the schedule mode change (e.g., fortonight only, and not other future occurrences of the scheduled modechange)). In some embodiments, the scheduled mode change applies to thecurrent day only, not the full schedule that includes repeatedoccurrences of the scheduled mode change. In some embodiments,activation of the selectable option that corresponds to an alarm for theend time of the scheduled mode change causes display of a user interfacethat is configured to accept user inputs to modify the start time of theschedule mode change as well, and optionally, user inputs to modifyother aspects of the scheduled mode change (e.g., sleep goal, full sleepschedule, etc.). In some embodiments, the selectable option thatcorresponds to the alarm has a first appearance when it is displayedwithout the selectable options corresponding to application functions;and has a second appearance when it is displayed among other selectableoptions corresponding to application functions. This is illustrated inFIGS. 9J-9L, for example, where the second user interface (e.g., thesleep screen 5083) includes a selectable option that corresponds to analarm for an end time of the scheduled mode change (e.g., the alarmaffordance 5086) and in response to detecting a fourth input (e.g., theuser input 5084, on the alarm affordance 5086), the computer systemdisplays a fourth user interface (e.g., the alarm application userinterface 9041) that includes user selectable options for modifying oneor more aspects of an upcoming occurrence of the schedule mode change(e.g., the link 9048). Displaying a user interface that includes userselectable options for modifying one or more aspects of an upcomingoccurrence of the scheduled mode change reduces the number of inputsneeded to perform an operation (e.g., adjusting the upcoming scheduledmode change without changing the future mode change). Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device, and makes the user-device interface more efficient,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination that the seconduser interface is displayed and that the current time corresponds to astart time of the scheduled mode change, the computer system replaces(6036) display of the second user interface with a fifth user interface(e.g., a sleep screen that is dimmed and has only the current date andno current time and no wake time indicators, and optionally reduced setof available actions) that corresponds to the restricted state (e.g.,screen-restricted state), wherein the fifth user interface includes areduced amount of user interface objects (e.g., current time, wake timeare removed on the sleep screen, the alarm indicator and applicationfunctions are optionally removed on the sleep screen, etc.) as comparedto the second user interface that corresponds to the restricted state.In some embodiments, the sleep screen optionally has fewer or differentset of application functions made available as compared to the wind downscreen. In some embodiments, the fifth user interface that correspondsto the restricted state of the computer system displayed during thescheduled mode change is a dark screen that includes only an indicationthat the Do-Not-Disturb mode is on. In some embodiments, the fifth userinterface is displayed in placed of the second user interface when thesecond user interface is displayed and the start time of the schedulemode change is reached. In some embodiments, if the user has not enabledthe wind down mode, or when the first preset time period is skipped, thecomputer system replaces display of the first user interface with thedisplay of the fifth user interface when the start time of the scheduledmode change is reached. In some embodiments, the Do Not Disturb mode isautomatically activated at the start of the first preset time period,and activated at the start of the scheduled mode change if the firstpreset time period is skipped or not enabled. In some embodiments, thecomputer system is a portable electronic device such as a mobile phoneor tablet device, and the computer system has a companion device, suchas a wearable device that is paired with the computer system. In someembodiments, when the schedule mode change occurs, the companion deviceis locked (e.g., screen-locked, such that regular input mechanisms forinteracting with the companion device are disabled). In someembodiments, a special predefined input (e.g., turning the digital crownof the company device to display a regular wake screen of the companiondevice) is required to re-enable the regular input mechanisms for thecompanion device. This is illustrated in FIG. 5O, for example, where thefifth user interface (e.g., the simplified sleep screen 5087) includes areduced amount of user interface objects (e.g., does not display thedate and time element 5012) as compared to the second user interfacethat corresponds to the restricted state (e.g., the sleep screen 5083shown in FIG. 5N). Replacing the second user interface with the fifthuser interface that includes a reduced amount of user interface objects,in accordance with a determination that the second user interface isdisplayed and that the current time corresponds to a start time of thescheduled mode change, performs an operation when a set of conditionshas been met without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, replacing the second user interface with the fifthuser interface includes (6038) gradually reducing luminance of thedisplay generation component from a first luminance level to a secondluminance level that is lower than the first luminance level. In someembodiments, the fifth user interface (e.g., sleep screen) is completelydark and only has a DND indicator (e.g., a dimmed moon icon) displayedon the screen. In some embodiments, the animated transition between thewind down screen and the sleep screen is triggered when the start timeof the scheduled sleep mode is reached. This is illustrated in FIGS.5N-50, for example, where the second user interface (e.g., the sleepscreen 5083) is displayed at a first luminance level, and is replaced bythe fifth user interface (e.g., the simplified sleep screen 5087)displayed at a second luminance level that is lower than the firstluminance level (e.g., as illustrated in the darker shading of thesimplified sleep screen 5087). Gradually reducing luminance of thedisplay generation component from the first luminance level to thesecond luminance level, when replacing the second user interface withthe fifth user interface, provides improved visual feedback to the user(e.g., indicating a successful update of user interface). Providingimproved visual feedback enhances the operability of the device andmakes the user-device interface more efficient, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, the first user interface and the second userinterface display (6040) the current time, and the fifth user interfacedoes not display the current time (but optionally displays the currentdate). In some embodiments, the first user interface and the second userinterface display a current date in addition to the current time, andthe fifth user interface does not display the current date or thecurrent time. This is illustrated in FIG. 5O, for example, where thefifth user interface (e.g., the simplified sleep screen 5087) does notdisplay the current time (e.g., does not display the date and timeelement 5012). Displaying the current time in the first user interfaceand the second user interface, but forgoing displaying the current timein the fifth user interface provides improved visual feedback to theuser (e.g., allowing the user to distinguish the fifth user interfacefrom the other user interfaces). Providing improved visual feedbackenhances the operability of the device and makes the user-deviceinterface more efficient, which, additionally, reduces power usage(e.g., fewer user interface objects are displayed) and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the second user interface includes (6042) aselectable user interface object (e.g., a button, an alarm icon, etc.)that, when activated, causes a container user interface object (e.g., apop up window, an action platter, a drop down menu, etc.) that includesone or more selectable options corresponding to preset applicationfunctions of one or more applications to be displayed, wherein the oneor more selectable options corresponding to the preset applicationfunctions, when activated, cause performance of the corresponding presetapplication functions. For example, in some embodiments, the actionplatter is displayed in a collapsed state or hidden on the second userinterface (e.g., the wind down screen, the wind up screen, etc.), andwhen the user taps on the user interface object corresponding to thehidden or collapsed action platter, the action platter is displayedshowing the different application functions that are available foraccess from the second user interface. In some embodiments, the actionplatter on the sleep screen is also hidden or collapsed, and the fullaction platter is displayed when the user taps on the user interfaceobject corresponding to the hidden or collapsed action platter. This isillustrated in FIGS. 5J-5K, for example, where the second user interface(e.g., the wind down screen 5013) includes the selectable user interfaceobject (e.g., the shortcut affordance 5033) that, when activated, causesa container user interface object (e.g., the action platter 5047) thatincludes one or more selectable options corresponding to presetapplication functions of one or more applications (e.g., the alarmoption 5054, the music option 5056, and the light option 5058) to bedisplayed. Displaying a container user interface object that includesone or more selectable options corresponding to preset applicationfunctions of one or more applications to be displayed, in response tothe user activating a selectable user interface object, reduces thenumber of inputs needed to perform an operation (e.g., activating apreset application function of an application). Reducing the number ofinputs needed to perform an operation enhances the operability of thedevice, and makes the user-device interface more efficient, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, at a first time, in accordance with a determinationthat the current time corresponds to an end time of the scheduled modechange: the computer outputs (6044) an indication that the end time ofthe scheduled mode change has been reached (e.g., generating an audio,tactile, and/or visual output that corresponds to an alarm for the waketime); the computer system displays a first selectable option to adjustthe end time of the scheduled mode change to a later time (e.g., snooze,temporarily stopping outputting the indication) and a second selectableoption to stop outputting the indication without adjusting the end timeof the scheduled mode change. At a second time later than the firsttime, the computer system detects a user input selecting a respectiveone of the first selectable option and the second selectable option; andin response to detecting the user input selecting the respective one ofthe first and second selectable options: in accordance with adetermination that the first selectable option was selected: thecomputer system maintaining display of the fifth user interface; andafter a predefined delay, the computer system outputs the indicationthat the adjusted end time of the scheduled mode change has beenreached; and in accordance with a determination that the secondselectable option was selected: the computer system displays a sixthuser interface that corresponds to the restricted state of the computersystem, wherein the sixth user interface is different from the fifthuser interface and the second user interface (e.g., the sixth userinterface is the good morning screen). In some embodiments, the sixthuser interface has a higher luminance than the second user interface andthe fifth user interface. In some embodiments, the second user interfacehas fewer user interface objects than the fifth user interface (e.g.,the sleep screen) and the first user interface (e.g., the regular wakescreen). In some embodiments, the sixth user interface displaysnotifications that were received and suppressed during the scheduledmode change (e.g., during the sleep mode) and optionally, during thepreset first time period (e.g., wind down period). In some embodiments,the sixth user interface also suppresses display of notifications. Insome embodiments, the sixth user interface (e.g., the good morningscreen) displays the current time, if the current time was not displayedon the fifth user interface (e.g., the sleep screen). In someembodiments, if the companion device of the computer system was lockedduring the scheduled mode change, the companion device becomes unlockedautomatically when the sixth user interface is displayed on the computersystem. This is illustrated in FIGS. 5P-5Q, for example, where the alarmnotification screen 5091 displays the first selectable option to adjustthe end time of the scheduled mode change to a later time (e.g., thesnooze button 5090) and a second selectable option to stop outputtingthe indication without adjusting the end time of the scheduled modechange (e.g., the dismiss button 5018). Maintaining the display of thefifth user interface or displaying the sixth user interface, inaccordance with a determination that the first or the second selectableoption was selected, performs an operation when a set of conditions hasbeen met without requiring further user input. Performing an operationwhen a set of conditions has been met without requiring further userinput controls enhances the operability of the device, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

FIGS. 7A-7J illustrate example user interfaces for generating batterycharging alerts during a preset time period before the start of thescheduled mode change, in accordance with some embodiments.

The examples in FIGS. 7A-7J are given in a scenario where userinterfaces are displayed on a first computer system (e.g., a portablemultifunction device 100) and a second computer system (e.g., aperipheral device 700). In some embodiments, the first computer systemis a portable electronic device, such as a mobile phone or tabletdevice, and the charging reminder is generated based on a first batterylevel (e.g., current battery level) of a companion device, such as awearable device (e.g., a watch, a bracelet, etc.), that is paired withthe portable electronic device, and the battery charging reminder is forincreasing the first battery level above the first preset battery level(e.g., a preset threshold level for supporting the sleep mode, anddifferent from (e.g., above) another lower threshold for a generalizedcharging reminder) is generated on the portable electronic device. Insome embodiments, the first computer system is a wearable device, suchas a watch or bracelet that is optionally paired with a portableelectronic device, the first battery level is a battery level of thewearable device, and the reminder for increasing the first battery levelabove the first preset battery level is generated on the wearabledevice. In some embodiments, the first battery level is a battery levelof the wearable device, and the reminder is generated on both theportable electronic device and the wearable device. In some embodiments,the first preset battery level is a preset static value (e.g., 30%, 40%,etc.) that is set irrespective of actual usage pattern of the firstcomputer system or companion device before and/or after the start of afirst preset time period. In some embodiments, the first preset batterylevel is a dynamic value that is established based on usage patternsand/or battery health of the first computer system or the companiondevice. For example, if the user consistently use the first computersystem actively during the wind down period and/or sleep period, thefirst preset battery level is set at a higher value than if the userdoes not often use the first computer system actively during the winddown period and/or sleep period. In some embodiments, if the firstcomputer system is a standalone electronic device (e.g., either thedevice 100 or the peripheral device 700), the first computer systemoptionally generates the charging reminders and/or battery statusindicators based on its own battery levels.

FIG. 7A illustrates that, before the wind down mode and sleep mode isstarted, the device 100 is in communication with the peripheral device700. A notification 5094 for a new message is displayed on a regularwake screen 5025 of the device 100, and a corresponding notification7006 is displayed on the peripheral device 700 (e.g., over a regularlock screen or restricted screen of the peripheral device 700). In someembodiments, the device 100 and the peripheral device 700 communicateregarding battery information, as shown in battery data 5009 beingtransmitted from the peripheral device 700 to the device 100 at acurrent time (e.g., 6:40 PM Tuesday) or another time proximate to thecurrent time (e.g., interval time periods in relation to the currenttime such as every five minutes, etc.). In this particular example, thepreset threshold battery level for supporting the sleep mode is set at30% of full battery charge for the peripheral device. At the currenttime that is outside of a preset time period (e.g., the wind downperiod, or a period that starts fifteen minutes before the start time ofthe wind down period (e.g., 9:00 PM on Tuesday) and ends 10 minutesbefore the start time of the sleep period (e.g., 10:00 PM on Tuesday))preceding the scheduled sleep time period (e.g., 10:00 PM on Tuesday to6:30 AM on Wednesday), Do Not Disturb mode is not activated and regularnotifications are still displayed, however, no notification or reminderis generated about charging the battery of the peripheral device (e.g.,currently at 28%) above the preset threshold battery level of 30% oneither the device 100 or on the peripheral device 700.

FIG. 7B illustrates that, in contrast to the example scenario shown inFIG. 7A, when the current time is within the preset time period (e.g.,between 8:45 PM and 9:50 PM on Tuesday) preceding the scheduled sleepperiod (e.g. scheduled to start at 10:00 PM on Tuesday), a bedtimereminder notification 7010 is generated on the peripheral device 700(and optionally on the device 100) in accordance with a determinationthat the first battery level (e.g., the current battery level of theperipheral device 700 at 28%) is below the preset threshold batterylevel (e.g., 30%) for supporting the sleep mode. In some embodiments,before the wind down mode is started, the multifunction device 100displays a current time and date 5012 on the regular wake screen 5025before the wind down mode is started and does not display any indicationregarding the battery charge of the peripheral device 700. In someembodiments, the multifunction device 100 displays a bedtime remindernotification as well. In some embodiments, the bedtime remindernotification 7010 includes reminders 7011 of the scheduled bedtime forthe upcoming sleep period, and the scheduled time for the wind downperiod that is coming up shortly. In some embodiments, the bedtimereminder notification 7010 includes a reminder 7013 for charging thedevice itself or its companion device above the current battery level(e.g., 28%) to at least the preset threshold battery level (e.g., 30%)before bedtime. In some embodiments, the bedtime reminder notification7010 optionally includes a reminder of whether a wakeup alarm has beenset for the upcoming sleep period. In some embodiment, the bedtimereminder notification 7010 includes an affordance to adjust the wakealarm setting. The bedtime reminder notification 7010 includes adismissal button 7012 that, when activated (e.g., by a tap input),causes dismissal of the bedtime reminder notification 7010. Before thewind down period is started, the wake screen of the device 100 and thewake screen of the companion device 700 can be dismissed using theregular dismissal input, once the bedtime reminder notification 7010 isdismissed using the dismiss button 7012.

FIG. 7C illustrates that, in contrast to FIG. 7A, when the current timeis within the wind down period (e.g., current time is 9:01 PM) precedingthe upcoming scheduled sleep period, charging reminders are displayed onboth the device 100 and the peripheral device 700. For example, inaccordance with a determination that the current time is within the winddown period (e.g., 1 hour before bedtime of 10:00 PM), the device 100displays a “good evening” message on the wind down screen 5013, whereinthe good evening message includes a battery level of the peripheraldevice 700 (e.g., watch battery level indicator 7014). In someembodiments, the battery level indicator 7014 is shown in accordancewith a determination that the first battery level (e.g., the batterylevel of the peripheral device 700) is below the preset thresholdbattery level for supporting the sleep mode (e.g., 30%). In someembodiments, if the first battery level is not below the presetthreshold battery level, the battery level indicator 7014 is notdisplayed on the wind down screen 5013. In some embodiments, the batterylevel indicator 7014 is displayed alternately with the bedtime reminder5020 (e.g., bedtime set for 10:00 PM, FIG. 5I) on the wind down screen5013. In some embodiments, a charge reminder 7016 is displayed on thewind down screen of the peripheral device 700 as well at the start ofthe wind down period, in accordance with a determination that the chargelevel of the peripheral device (or optionally the charge level of themultifunction device 100) is below a preset threshold battery level. Thecharge reminder 7016 optionally specifies the current battery level 7013of the peripheral device 700 (or optionally the charge level of themultifunction device 100) and the threshold battery level (e.g., 30%)for supporting the sleep mode. In some embodiments, the charge reminder7016 optionally includes a wake alarm indicator that indicates the wakealarm setting for the upcoming sleep period, and a dismiss button 7018for dismissing the charge reminder 7016. In some embodiments, thethreshold battery level is set to ensure sufficient charge to last theduration of the sleep mode time period and providing the wake alarm. Insome embodiments, when the charge reminder 7016 is dismissed before thestart time of the sleep period is reached, the peripheral devicedisplays its wind down screen user interface. In some embodiments,charge reminder 7016 is automatically dismissed without user input whenthe peripheral device is connected to a charger. In some embodiments,the battery level indicator 7014 is displayed on the wind down screen5013 of the multifunction function device 100 for as long as the batterylevel of the peripheral device 700 (or its own battery level) remainsbelow the preset threshold battery level (e.g., 30%). In someembodiments, the battery level indicator 7014 is displayed on the winddown screen 5013 of the multifunction function device 100 when thebattery level of the peripheral device 700 (or its own battery level)rises above the preset threshold battery level (e.g., 30%) during thewind down period. In some embodiments, the battery level indicator 7014ceases to be displayed on the wind down screen 5013 of the multifunctionfunction device 100 when the current time is within a preset time periodbefore the start time of the scheduled sleep period (e.g., 10 minutesbefore 10:00 PM) when there is insufficient time to charge the batteryto a level above the preset threshold battery level before the sleepperiod is started. These features may help to reduce excess stress aboutcharging the peripheral device right before bedtime.

FIG. 7D illustrates that, in some embodiments, during the preset timeperiod before the start of the scheduled sleep period (e.g., during thewind down period, or during the time 15 minutes before wind down periodstarts till 10 minutes before sleep period starts, etc.), if the batterylevel of the device for which charging reminder is displayed hasincreased to above the preset threshold level (e.g., 30%,) or is fullycharged, the device 100 and/or peripheral device 700 displays anotherbattery level reminder to inform the user that there is sufficientbattery charge to support the upcoming sleep mode time period andoptionally the wake alarm. In some embodiments, as shown in FIG. 7E, thedevice 100 displays a battery level indicator 7014 on the wind downscreen 5013. In some embodiments, the battery level indicator 7014indicates the battery level of the peripheral device 700 (and/or its ownbattery level). In some embodiments, the peripheral device displays anotification 7019 to notify the user that the peripheral device 700 (orthe multifunction device 100) has been charged to a sufficient level(e.g., above the preset threshold battery level, or fully charged,etc.). In some embodiments, the notification 7019 is displayed with adismiss button 7018. When the dismiss button is activated, theperipheral device 700 redisplays its wind down screen 7022, inaccordance with some embodiments. In some embodiments, the wake screenof the peripheral device includes a time element showing the currenttime, and a DND indicator 7020 on a dimmed touch screen 712.

FIG. 7F illustrates user interfaces for the first computer system andthe second computer system when the current time is right before (e.g.,1 minute before) the scheduled mode change (e.g., the start of thescheduled sleep period). In FIG. 7F, a bedtime reminder 7010 isgenerated on the peripheral device 700 that does not include batterystatus information for either the multifunction device 100 or theperipheral device 700 (e.g., irrespective of whether battery level ofeither the multifunction device 100 or the peripheral device 700 isbelow the present threshold level to support the sleep mode through thesleep period and generate the wake alarm). In some embodiments, thebedtime reminder is only generated on the peripheral device 700 and noton the multifunction device 100, when the current time is right before(e.g., one minute before) the start of the scheduled sleep period. Insome embodiments, the bedtime reminder 7010 includes an indication ofthe wake alarm setting for the end of the sleep period. In someembodiments, the bedtime reminder 7010 is displayed with a dismissbutton 7012. In some embodiments, the peripheral device dismisses thebedtime reminder 7010 and displays the sleep screen for the peripheraldevice (e.g., sleep screen 7028, optionally the same as the wind downscreen 5022). In some embodiments, if the bedtime reminder 7010 is notmanually dismissed by an input on the dismiss button 7012, theperipheral device 700 automatically dismisses the bedtime reminder 7010when the scheduled bedtime is reached (e.g., at 10:00 PM).

FIG. 7G illustrates the sleep screen 5083 of the device 100 and thesleep screen 7028 of the peripheral device 700 (e.g., optionally thesame as the wind down screen 7022). In some embodiments, the sleepscreen 5083 no longer displays the bedtime information or the alarminformation for the upcoming sleep period. In some embodiments, thesleep screen 5083 has a reduced display luminosity level as compared tothe wind down screen 5013 displayed during the wind down period. In someembodiments, the sleep screen 5083 includes time and date element 5012,and optionally, a shortcut or action affordance for displaying a set ofapplication functions that are still available on the sleep screen. Insome embodiments, the sleep screen 5083 includes a dismiss button fordismissing the sleep screen and navigate to a regular wake screen duringthe sleep period. In some embodiments, the user interface elements shownon the sleep screen 5083 have a diminished appearance as compared totheir counterparts on the wind down screen 5013. In some embodiments,the sleep screen on the peripheral device 700 has the same appearance ofthe wake screen on the peripheral device 700. In some embodiments, thesleep screen on the peripheral device is dismissed using a presetgesture (e.g., turning the digital crown 7002 until a threshold isreached), e.g., as described with respect to FIGS. 11A-11AF andaccompanying descriptions. In some embodiments, the sleep screen of theperipheral device 700 is a completely dark screen, optionally, with onlythe DND indicator 7020 displayed. In some embodiments, the sleep screen700 of the peripheral device 700 has fewer user interface objects and/orsupports fewer types of inputs as compared to the regular wake screen orlock screen of the peripheral device 700, and/or as compared to the winddown screen of the peripheral device 700. In some embodiments, the sleepscreens of the multifunction device 100 and the peripheral device 700are only displayed in response to a wake input, and during a prolongedperiod of inactivity, the displays of the multifunction device 100 andthe peripheral device are in an off state or low power always-on statethat includes only the current time and/or the DND indicator 7020.

In some embodiments, as shown in FIG. 7G, when the current time iswithin the scheduled sleep period, even if the current battery level(e.g., 15%) of the peripheral device 700 (and optionally, the batterylevel of the multifunction device 100) falls below the preset thresholdbattery level (e.g., 30%), the peripheral device 700 and themultifunction device 100 does not display any charging reminder oralerts regarding the battery level (e.g., sleep screen is maintained, orscreen is dark or in the low power mode). This behavior is distinguishedfrom conventional low battery reminders that are displayed any time thatthe battery is sufficiently low (e.g., the conventional low batterythreshold is set much lower than the preset threshold battery level forsupporting the sleep mode and optionally the wake alarm). This is alsodistinguished from low battery reminders that are generated any timethat the battery is low for a future scheduled event. Suppressing thereminders for increasing the battery level during the scheduled sleepperiod may prevent the reminder for increasing the battery level fromcausing unnecessary stress (e.g., keeping a user awake past a scheduledbedtime to charge the device(s)).

FIG. 7H illustrates generation of an alarm output when the scheduledwake time for the sleep period is reached, ending sleep mode for thedevice. In some embodiments, when an alarm is set for the wake time ofthe sleep period, the alarm goes off on the peripheral device 700 first(e.g., at exactly the scheduled wake time 6:30 AM). In some embodiments,when the wake alarm goes off on the peripheral device 700, the alarmscreen 7030 is displayed in conjunction with a non-visual output, suchas a tactile output and or an audio output. In some embodiments, thealarm screen 7030 includes an affordance (e.g., stop button 7032) that,when activated, causes the peripheral device 700 to stop the alarmoutput on the peripheral device 700, and navigate to a good morningscreen 7038 (FIG. 7J) on the peripheral device 700. In some embodiments,if the good morning screen 7038 is not enabled on the peripheral device700, the peripheral device navigates to the regular wake screen for theperipheral device 700. In some embodiments, the alarm screen alsoincludes an affordance (e.g., a snooze button 7034) that, whenactivated, causes the peripheral device 700 to reset the wake time to apreset amount of time (e.g., 5 minutes, 7 minutes, etc.) after theoriginally scheduled end time of the sleep period, maintaining sleepmode for the device for that additional preset amount of time. In someembodiments, in response to an input dismissing the alarm output (e.g.,turning the alarm off) using the stop button 7032 on the peripheraldevice 700, before the alarm output is generated on the multifunctiondevice 100, the alarm output on the multifunction device 100 is canceledbefore it is generated. In some embodiments, in response to an inputthat resets the wake time to a later time using the snooze button 7034,the alarm output on the multifunction device 100 is delayed by the sameamount of time before it is generated. In some embodiments, there is nodelay between the alarm outputs on the multifunction device 100 and theperipheral device 100, and in such embodiments, snoozing or stopping thealarm output on either of the multifunction device 100 and theperipheral device 700 causes the alarm output on the other device to besnoozed or stopped as well (e.g., the input adjusts the end time of thesleep mode, or causes transition out of the sleep mode, which is appliedto both the multifunction device 100 and the peripheral device 700).

FIG. 7I shows that, in some embodiments, the alarm output on themultifunction device 100 is generated slightly after (e.g., 5 seconds,10 seconds, etc.) the alarm output on the peripheral device 700. If thealarm output on the peripheral device 700 was not stopped or snoozedbefore the alarm output is generated on the multifunction device 100,both the multifunction device 100 and the peripheral device 700 generatetheir respective alarm output at the same time after the initial delayperiod (e.g., 5 seconds, 10 seconds, etc.). In some embodiments, asshown in FIG. 7I, the alarm screen 5091 is displayed at a time slightlyafter (e.g., 5 seconds, 10 seconds, etc.) the scheduled end time of thesleep period. The alarm screen 5091 displayed on the multifunctiondevice 100 includes the current time and date in the time and dateelement 5012, alarm text 5095, a snooze button 5090 for delaying the endtime of the sleep period by a preset amount of time (e.g., 5 minutes, 7minutes, etc.), and a dismiss button 5018 for stopping the alarm outputand navigate to the regular wake screen 5019 (if a good morning mode isnot enabled after sleep mode) or the good morning screen 5093 (if a goodmorning mode is enabled after sleep mode). In some embodiments, thealarm output generated on the multifunction device 100 includes one ormore tactile outputs and/or audio outputs, in conjunction with the alarmscreen 5091. In some embodiments, while the alarm outputs areconcurrently generated on both the multifunction device 100 and theperipheral device 700, snoozing or stopping the alarm output on eitherof the multifunction device 100 and the peripheral device 700 causes thealarm output on the other device to be snoozed or stopped as well.

As shown in FIG. 7J, alarm output can be stopped on both themultifunction device 100 and the peripheral device 700, in response toeither a tap input by contact 5026 on the dismiss button 5018 on thealarm screen 5091 of the multifunction device 100, or a tap input by acontact 7036 on the stop button 7032 on the alarm screen 7030 shown onthe peripheral device 700. As a result, on the multifunction device 100,if the good morning mode (or windup mode) is enabled, the good morningscreen 5093 is displayed, showing weather information 5022 and dismissbutton 5018. The good morning screen 5093 will be displayed during thewindup mode in response to the multifunction device 100 being woken byuser input, until the windup mode is terminated at its scheduled endtime, or manually terminated. In some embodiments, the windup mode isended when the dismiss button 5018 is activated for the first time. Insome embodiments, after the alarm screen 7030 of the peripheral device700 is dismissed, the good morning screen 7038 of the peripheral device700 is displayed during the scheduled windup period (e.g., one hourafter the end time of the sleep period). In some embodiments, the goodmorning screen 7038 on the peripheral device 700 includes some weatherinformation 7037 for the day, a battery status information (e.g.,current battery level of the peripheral device 700 is 5%) or chargereminder 7039 for charging the battery of the peripheral device 700 (andoptionally the same information and reminder for the multifunctiondevice 100). In some embodiments, the good morning screen 7038 of theperipheral device 700 optionally displays a summary of how the user hasadhered to the sleep schedule for the past several days (e.g., sevendays, 10 days, two weeks, etc.) to indicate a trend or overall sleepquality of the user. In some embodiments, a summary 7041 is onlygenerated if the user has consistently met a pre-established sleep goalfor the sleep schedule. In some embodiments, the good morning screen7038 of the peripheral device 700 displays the summary 7041 summarizingthe sleep quality for the most recently completed sleep period astracked by the peripheral device 700. In some embodiments, the goodmorning screen 7038 only includes the summary 7041 if the sleep goal ismet during the most recently completed sleep period. In someembodiments, coaching messages about sleep are displayed on the goodmorning screen and are based on recorded sleep data for multipleconsecutive days of the active sleep schedule that indicate satisfactionof a preset sleep goal (e.g., a “streak”).

In some embodiments, if the alarm output on either one of the first orsecond computer system (e.g., the multifunction device 100 and theperipheral device 700) is not generated due to low battery level (or nobattery) at said one of the first or second computer system, the alarmoutput is still generated at the other of the first or second computersystem. For example, if peripheral device 700 runs out of battery duringthe scheduled sleep time period, the device 100 still generates thealarm output. Alternatively, if the device 100 runs out of batteryduring the scheduled sleep time period, the peripheral device 700 stillgenerates the alarm output. In some embodiments, if the alarm output onthe first computer system is not generated due to low battery level ofthe first computer system, the alarm output is generated at the secondcomputer system without the delay. For example, if peripheral device 700runs out of battery during the scheduled sleep time period, the device100 generates the alarm output without a delay.

FIGS. 8A-8D are flowchart diagrams of a method 8000 of generatingbattery charging alerts during a preset time period before the start ofthe scheduled mode change, in accordance with some embodiments.

This method relates to displaying or forgoing displaying a reminder forincreasing battery level, based on comparison of the current batterylevel with a preset battery threshold level, and the current time withthe first preset period preceding a schedule mode change. Displaying orforgoing displaying the reminder for increasing battery level based onthe comparisons performs an operation when a set of conditions has beenmet without requiring further user input improves the operation of thecomputer system to support its intended functions (e.g., tracking sleepduring the sleep period and outputting the wake alarm withoutunexpectedly running out of power before doing so). This method isillustrated in FIGS. 7A-7C, for example, where the charge reminder ifonly generated when the battery level dropped below 30% while thecurrent time is within a preset time period preceding the scheduledsleep period of an active sleep schedule.

The method 8000 is performed at a first computer system in communicationwith a first display generation component (and, in some embodiments, oneor more input devices, and/or a peripheral device (e.g., a wearabledevice, such as a wrist band, a watch, a pin, a ring, etc.) that iscoupled to the computer system (e.g., paired via a Bluetooth connection,a WiFi connection, etc., and performs operations (e.g., transmitrequested information, displaying alerts and notifications, displaysreceived information, etc.) in accordance with instructions and/orqueries received from the computer system). In some embodiments, thefirst computer system, the first display generation component, and theone or more input devices are integrated into a single portableelectronic device with a common housing, such as in a hand held device,a table device, a smart phone, etc. In some embodiments, the peripheraldevice is a wearable device that is paired and in communication with theportable electronic device. In some embodiments, the first computersystem is a wearable device that includes a display generation componentand one or more input devices. In some embodiments, the first computersystem is a peripheral device (e.g., a wearable device) that is coupledto a portable electronic device. In the method 8000, in accordance witha determination that a current time is within (e.g., after the starttime of and before the end time of) a first preset time period (e.g., atime range that starts at x amount of time (e.g., 1 hour, 45 minutes,etc.) before the start time of the scheduled mode change, and ends at yamount of time (e.g., 10 minutes, 5 minutes, 0 minute, etc.) before thestart time of the scheduled mode change, a wind down period (e.g., 1hour, 45 minutes, etc.), a preset time period (e.g., 90 minutes, 1 hour,etc.) etc.) preceding (e.g., having an end time that is the same as orimmediately before a start time of a respective scheduled time period,having an end time that is before but not necessarily immediately beforethe start time of a respective scheduled time period, etc.) a scheduledmode change (e.g., a first scheduled time period (e.g., a first sleepschedule, a first DND time period, etc.)) and in accordance with adetermination that a first battery level (e.g., the battery level of thefirst computer system itself, the battery level of a peripheral devicecoupled to the first computer system, etc.) is below a first presetbattery level (e.g., a first fixed threshold battery level, adynamically determined threshold batter level, etc.), the computersystem displays (8002), via the first display generation component, areminder for increasing the first battery level above the first presetbattery level (e.g., a reminder for charging a peripheral device (e.g.,displaying the charging reminder on the wind down wake screen of theportable electronic device, and/or the peripheral device)). Inaccordance with a determination that the current time is outside of(e.g., before the start time of) the first preset time period precedingthe scheduled mode change (e.g., the first scheduled time period) and inaccordance with a determination that the first battery level (e.g., thebattery level of the computer system itself, the battery level of aperipheral device coupled to the computer system, etc.) is below thefirst preset battery level (e.g., a first fixed threshold battery level,a dynamically determined threshold batter level, etc.), the computersystem forgoes (8004) display of the reminder for increasing the firstbattery level above the first preset battery level (e.g., the chargingreminder is not displayed on a regular wake screen user interface, or onthe wake screen user interface shown during the sleep mode, even whenthe battery level cannot sustain through the whole duration of the sleepmode). In some embodiments, the first computer system is a portableelectronic device, such as a mobile phone or tablet device, the firstbattery level is a battery level of the portable electronic device, andthe reminder for increasing the first battery level above the firstpreset battery level is generated on the portable electronic device. Insome embodiments, the first computer system is a portable electronicdevice, such as a mobile phone or tablet device, the first battery levelis a battery level of a companion device, such as a wearable device(e.g., a watch, a bracelet, etc.), that is paired with the portableelectronic device, and the reminder for increasing the first batterylevel above the first preset battery level is generated on the portableelectronic device. In some embodiments, the first computer system is awearable device, such as a watch or bracelet that is optionally pairedwith a portable electronic device, the first battery level is a batterylevel of the wearable device, and the reminder for increasing the firstbattery level above the first preset battery level is generated on thewearable device. In some embodiments, the first battery level is abattery level of the wearable device, and the reminder is generated onboth the portable electronic device and the wearable device. In someembodiments, the first preset battery level is a preset static value(e.g., 30%, 40%, etc.) that is set irrespective of actual usage patternof the first computer system or companion device before and/or after thestart of the first preset time period. In some embodiments, the firstpreset battery level is a dynamic value that is established based onusage patterns and/or battery health of the first computer system or thecompanion device. For example, if the user consistently use the firstcomputer system actively during the wind down period and/or sleepperiod, the first preset battery level is set at a higher value than ifthe user does not often use the first computer system actively duringthe wind down period and/or sleep period.

In some embodiments, in accordance with a determination that the currenttime is within the scheduled mode change (e.g., within the firstscheduled time period (e.g., a first sleep schedule, a first DND timeperiod, etc.)) and in accordance with a determination that a secondbattery level (e.g., the battery level of the computer system itself,the battery level of a peripheral device coupled to the computer system,etc.) is below a second preset battery level (e.g., a second fixedthreshold battery level, a dynamically determined threshold batterlevel, etc.), the computer system forgoes (8006) displaying the reminderfor increasing the second battery level above the second preset batterylevel. This behavior is distinguished from regular low battery remindersthat is displayed any time that the battery is sufficiently low (e.g.,this threshold is set much lower than the first preset level), and fromlow battery reminders that is generated any time that the battery is lowfor a future scheduled event. This is illustrated in FIG. 7G, forexample, where the current time is within the schedule mode change(e.g., during a sleep schedule starting at 10:00 PM) and in accordancewith a determination that the second battery level (e.g., 15% batteryfor the peripheral device 700) is below a second preset battery level(e.g., 30%), the first computer system (e.g., the portable multifunctiondevice 100) forgoes displaying the reminder for increasing the secondbattery level above the second preset battery level. Forgoing displayingthe reminder for increasing the second battery level above the secondpreset battery level, when the current time is within the scheduled modechange, performs an operation (e.g., silencing the reminder to chargebattery) when a set of conditions has been met without requiring furtheruser input. Performing an operation when a set of conditions has beenmet without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, a start time of the scheduled mode change is (8008)adjustable (e.g., to a second scheduled time period with a second starttime and/or a second end time). In some embodiments, the first computersystem detects one or more inputs that correspond to a request to adjustthe start time and optionally the end time of the scheduled mode change(e.g., the input includes a tap input on the wake alarm icon on the winddown screen that leads to an alarm user interface for adjusting thesleep schedule for the current day, where additional user inputs arereceived to adjust the start time and/or end time of the sleep periodfor the current day), and in response to detecting that the one or moreinputs that correspond to the request to adjust the start time of theschedule mode change: the first computer system adjusts start and endtimes of the first preset time period in accordance with the adjustedstart time of the scheduled mode change. This is shown in FIGS. 9J-9M,for example, where activating the alarm affordance 5086 displays a userinterface (e.g., the alarm application user interface 9041) foradjusting the start time of the scheduled mode change. Allowing thestart time of the scheduled mode change to be adjustable reduces thenumber of inputs needed to perform an operation. Reducing the number ofinputs needed to perform an operation enhances the operability of thedevice, and makes the user-device interface more efficient, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the reminder for increasing the first battery levelabove the first preset battery level is (8010) displayed concurrentlywith a reminder that the scheduled mode change is about to start. Insome embodiments, the reminder for increasing the first battery leveland the reminder that the scheduled mode change is about to start aredisplayed, via the first display generation component, in a first userinterface that corresponds to a restricted state of the computer system(e.g., in the restricted state (e.g., a screen-locked state, orscreen-restricted), interaction with graphical user interfaces of thecomputer system is restricted or blocked by a lock screen, a wake screenin the authenticated state and/or the unauthenticated state, acoversheet user interface, etc.). In some embodiments, the reminder forincreasing the first battery level and the reminder that the scheduledmode change is about to start are displayed, via the first displaygeneration component, in a notification that overlays a first userinterface that corresponds to a restricted state of the computer system.This is shown in FIG. 7B, for example, where the reminder for increasingthe first battery level (e.g., the (charging) reminder 7013) isdisplayed concurrently with the reminder that the scheduled mode changeis about to start (e.g., the bedtime reminder 7011). Displaying thereminder for increasing the first battery level above the first presetbattery level concurrently with the reminder that the scheduled modechange is about to start performs an operation when a set of conditionshas been met without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the reminder for increasing the first battery levelabove the first preset battery level is (8012) displayed concurrentlywith a reminder that the scheduled mode change is about to start on afirst user interface that corresponds to a restricted state of the firstcomputer system. In the method 8000, while displaying the first userinterface that corresponds to the restricted state of the first computersystem, the computer system detects a first user input directed to thefirst user interface. In response to detecting the first user inputdirected to the first user interface: in accordance with a determinationthat the first input meets first criteria, the computer system replacesdisplay of the first user interface with a second user interface thatcorresponds to the restricted state of the first computer system (e.g.,a screen-locked or screen-restricted state of the first computersystem), wherein the second user interface is different from the firstuser interface. In some embodiments, the first user interface displays areminder that a scheduled mode change (e.g., sleep mode) is about tostart at a preset start time of the scheduled mode change. In someembodiments, the first user interface displays a reminder that a winddown period preceding the scheduled mode change is about to start at apreset start time of the wind down period. In some embodiments, thefirst user interface is a bedtime reminder user interface that isdifferent from the wind down screen. In some embodiments, the first userinterface is the wind down screen that is displayed during the wind downperiod preceding the scheduled sleep mode. In some embodiments, thefirst user interface displays the first battery level only when thefirst battery level is below the first preset battery level and does notdisplay the first battery level when the first battery level is notbelow the first preset battery level. In some embodiments, the firstuser interface is a wind down screen and the second user interface is aregular lock screen, a wake screen that corresponds to an authenticatedstate, a wake screen that corresponds to an unauthenticated state.Dismissing the wind down screen using a predefined input causes displayof the regular lock screen or wake screen. In some embodiments, thefirst user interface is a reminder screen and the second user interfaceis the wind down screen, and dismissal of the reminder screen using apredefined input causes display of the wind down screen, and dismissalof the wind down screen using a predefined input causes display of theregular lock screen or wake screen. Replacing the display of the firstuser interface with a second user interface that corresponds to therestricted state of the first computer system, in accordance with thedetermination that the first input meets the first criteria, performs anoperation when a set of conditions has been met without requiringfurther user input. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the reminder for increasing the first battery leveland the reminder that the scheduled mode change is (8014) about to startare displayed, via the first display generation component, in anotification that overlays a first user interface that corresponds to arestricted state of the computer system. In some embodiments, the firstuser interface is a regular lock screen or wake screen. In someembodiments, the first user interface is a wind down screen that isdisplayed before the start time of the scheduled mode change. In someembodiments, the notification is dismissed in response to an input thatmeet the criteria for dismissing other types of notifications as well.This is shown in FIG. 7B, for example, where the reminder for increasingthe first battery level (e.g., charging reminder 7013) and the reminderthat the scheduled mode change is about to start (e.g., the bedtimereminder 7011) are displayed in a notification (e.g. the bedtimereminder notification 7010) that overlays a first user interface thatcorresponds to a restricted state of the computer system (e.g., a lockscreen). Displaying the reminder for increasing the first battery leveland the reminder that the scheduled mode change is about to start, inthe notification that overlays the first user interface that correspondsto the restricted state of the computer system, provides improved visualfeedback to the user (e.g., allowing the user to see both reminders inthe same user interface). Providing improved visual feedback enhancesthe operability of the device and makes the user-device interface moreefficient, which, additionally, reduces power usage (e.g., fewer userinterface objects are displayed) and improves battery life of the deviceby enabling the user to use the device more quickly and efficiently.

In some embodiments, the first battery level is (8016) a battery levelof a second computer system distinct from the first computer system, andwherein the first computer system displays the reminder increasing thefirst battery level above the first preset battery level in a userinterface that corresponds to a restricted mode of the first computersystem (e.g., on a wind down screen, a bedtime reminder screen that isdisplayed close to the start time of the wind down period, a bedtimereminder screen that is displayed close to the start time of the sleepmode (e.g., if wind down period is not enabled), etc.). In someembodiments, the first computer system is a portable electronic device,such as a mobile phone or tablet device, and the second computer systemis a companion device, such as a wearable device, that is paired withthe portable electronic device. In some embodiments, after thedisplaying the reminder, the first computer system displays thecurrent/updated battery status of the companion device only when thecompanion device is being charged. This is illustrated in FIGS. 7C and7D, for example, where the battery status of the peripheral device 700is displayed on the wind down screen 5013 of the multifunction device100. Displaying the reminder for increasing the first battery level ofthe second computer system above the first preset battery level on thefirst computer system performs an operation when a set of conditions hasbeen met without requiring further user input. Performing an operationwhen a set of conditions has been met without requiring further userinput controls enhances the operability of the device, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, at a time after displaying the reminder, inaccordance with a determination that the current time is within thefirst preset time period preceding the scheduled mode change and inaccordance with a determination that a third battery level (e.g., thecurrent battery level of the first computer system, the current batterylevel of a second computer system that is paired with the first computersystem, etc.) is at or above a third preset battery level (e.g., fullycharged, or above the first preset battery level), the computer systemdisplays (8018), via the display generation component, a notification ofthe third battery level (e.g., an indication that the device associatedwith the battery is sufficiently charged (e.g., fully charged, orcharged to a level above the first preset battery level, etc.) tosupport successful completion of the scheduled mode change on the firstcomputer system or a second computer system that is paired with thefirst computer system). In some embodiments, the first computer systemdisplays a current battery level of the first computer system or asecond computer system that is paired with the first computer systemafter the completion of the scheduled mode change (e.g., on the goodmorning screen), and optionally displays a prompt for the user toincrease the current battery level of the first computer system or thesecond computer system. This is shown in FIG. 7D, for example, where athird battery level (e.g., 30% charge for the peripheral device 700) isat or above a third preset battery level (e.g., 30%) and the computersystem displays a notification of the third battery level (e.g., thenotification 7019). Displaying the notification of the third batterylevel when the battery level is at or above the third preset batterylevel and the current time is within the first preset time periodperforms an operation when a set of conditions has been met withoutrequiring further user input. Performing an operation when a set ofconditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first computer system is (8020) paired with asecond computer system, the first battery level is a battery level ofthe second computer system. In the method 8000: at a time afterdisplaying the reminder, in accordance with a determination that afourth battery level of the second computer system is at or above afourth preset battery level (e.g., fully charged, or above the firstpreset battery level), the computer system displays, via the displaygeneration component, a notification of the third battery level. Forexample, after the second computer system (e.g., the paired wearabledevice) is connected to a charger, the first computer system is used tooutput an alert to the user to let the user know that the secondcomputer system is charged above a sufficient level so that the user canput the second computer system on again. In some embodiments, thenotification is only displayed during certain time periods, e.g.,outside of the sleep mode and outside the wind down period. In someembodiments, the notification is only displayed during the good morningperiod. This is shown in FIG. 7D, for example, where the fourth batterylevel (e.g., 30%) is at or above a fourth preset battery level (e.g.,30%) and the first computer system (e.g., the portable multifunctiondevice 100) displays, via the display generation component (e.g., thetouch screen 712 of the peripheral device 700) a notification of thebattery level of the peripheral device 700 (e.g., battery levelindicator 7014). Performs an operation when a set of conditions has beenmet without requiring further user input. Performing an operation when aset of conditions has been met without requiring further user inputcontrols enhances the operability of the device, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

FIGS. 9A-9AG illustrate example user interfaces for configuring one ormore modes described herein, in accordance with some embodiments.

FIG. 9A illustrates an exemplary user interface for setting a sleep goalfor one or more sleep schedules managed by the multifunction device 100and optionally the peripheral device 700, in accordance with someembodiments. In some embodiments, the sleep schedule and relatedoperation modes are managed by an application installed on themultifunction device 100 and optionally the peripheral device 700. Whenthe application is launched without a sleep schedule having been set up,a sleep goal user interface 9001 is displayed first to prompt the userto specify a sleep goal—an amount of time that the user would like tosleep each night. This sleep goal is used to measure how a sleep periodof a sleep schedule compares with the user's desired amount of sleep foreach day. In some embodiments, the sleep goal user interface 9001includes sleep goal information 9002 to explain the purpose of the sleepgoal. In some embodiments, the sleep goal user interface includes asleep goal indicator 9004. In some embodiments, the sleep goal indicator9004 includes affordances (e.g., minus button 9006 and plus button 9008)for decreasing or increasing the sleep goal duration and an indicationof the current duration of the sleep goal. In some embodiments, thesleep goal user interface 9001 provides an initial value for the sleepgoal that the user can adjust. In some embodiments, the sleep goal userinterface provides no initial value for the sleep goal, and the user canenter any amount this within a preset range (e.g., between 4 hours and12 hours). In some embodiments, the sleep goal user interface 9001includes an affordance (e.g., “next” button 9010) for confirming thespecified sleep goal and navigating to the next stage of the set upprocess. Additional steps for establishing a sleep schedule or multiplesleep schedules and associated operation modes after establishing thesleep goal are described are described with respect to FIGS. 9Q-9AG andaccompanying descriptions.

FIGS. 9B-9I illustrate how the multifunction device 100 (and optionallythe peripheral device 700) indicate to the user that a currentlyadjusted sleep schedule does or does not meet the pre-established sleepgoal specified by the user, in accordance with some embodiments.

FIG. 9B illustrates an exemplary sleep schedule user interface 9011 forsetting a sleep schedule (e.g., sleep schedule 1 which is used in otherexamples of this disclosure, or another sleep schedule for other days ofthe week, etc.). In some embodiments, the sleep schedule user interface9011 includes a day selection region 9012 in which the days to which thecurrently specified schedule is applied are indicated and optionally areeditable in response to user input. For example, currently the sleepschedule applies to all five weekdays, and does not apply to the weekenddays. In some embodiments, the sleep schedule user interface 9011includes a bedtime indicator 9014 (e.g., showing the start time of thesleep period of the current sleep schedule), a wake time indicator 9016(e.g., showing the end time of the sleep period of the current sleepschedule), a sleep time adjuster object 9036 (e.g., a clock face 9018with a slider channel around its periphery, other object that dividesthe time of a day into multiple units of time (e.g., 5 minutesincrement, half hour increment, etc.) and distributes them along aslider or dial, a set of textual input fields for the start time and endtime for the sleep period, etc.). In some embodiments, the sleepschedule user interface 9011 optionally includes a textual sleep goalmessage 9030 indicating whether the current sleep period as specifiedmeets the pre-established sleep goal. In some embodiments, the sleepschedule user interface 9011 includes a textual object (e.g., optionallyshown in the center of the clock face, or at another area (e.g., in thesleep goal message 9030, or standalone, etc.) of the sleep schedule userinterface 9011) indicating the current duration of the sleep period asspecified. In some embodiments, the sleep schedule user interface 9011includes a wake alarm affordance 9032 that enables or disables the wakealarm for the current sleep schedule. In some embodiments, the sleepschedule user interface 9011 includes a snooze selection affordance 9034that enables or disables a snooze function for an established wakealarm. In some embodiments, as shown in FIG. 9B, the sleep time adjusterobject 9036 includes a first object 9024 that can be adjusted (e.g.,optionally either by dragging the first object 9024 itself along oraround the sleep time adjuster object 9036, or by entering a value usingthe bedtime indicator 9014, etc.) to set the start time of the sleepperiod, and the sleep time adjuster object 9036 also includes a secondobject 9026 that can be adjusted (e.g., optionally either by draggingthe second object 9026 itself along or around the sleep time adjusterobject 9036, or by entering a value using the wake time indicator 9016,etc.). In some embodiments, a sleep duration indicator 9022 is displayed(e.g., along or around the sleep time adjustor object 9036 between thefirst object 9024 and the second object 9026) to indicate the fractionand position of the sleep period relative to a 12-hour period (e.g.,evening to morning). In some embodiments, the sleep time adjuster objectincludes a control to switch the 12-hour period from centered aroundmidnight to be centered around noon (e.g., (1) centered around midnightmeans that the time period is from midnight to noon and (2) centeredaround noon means that the time period is from noon to midnight). Insome embodiments, the sleep time adjuster object displays a totalduration of a 24-hour period for each sleep period, and the first objectand the second object indicating the bedtime and wake time of a sleeptime period of a sleep schedule is configured to move along or aroundthe sleep time adjuster object through the 24-hour period, includinglocations corresponding to midnight and noon on a particular day ormilitary time (e.g., 0-23 hour). In some embodiments, the sleep timeadjuster object include a 24-hour clock face that includes a 12 o'clocklocation at 0 degrees (e.g., at the top) and another 12 o'clock locationat 180 degrees (e.g., at the bottom), and indications near the 0 degreeslocation and the 180 degrees location to indicate whether the 12 ismidnight or noon (e.g., the indication proximate to the 0 degreeslocation includes a moon and the indication proximate to the 180 degreeslocation includes a sun). In some embodiments, as the first object 9024is moved along or around the sleep time adjuster object 9036, the starttime of the sleep period is updated according to the position of thefirst object 9024, as shown by the value of the bedtime indicator 9014;and as the second object 9026 is moved along or around the sleep timeadjuster object 9036, the end time of the sleep period is updatedaccording to the position of the second object 9026, as shown by thevalue of the wake time indicator 9016. The size of the sleep durationindicator 9022 grows and shrinks, and the total duration of the sleepperiod changes, in accordance with the movement of the first object 9024and the second object 9026. In some embodiments, the sleep time adjusterobject 9036 (e.g., the clock face with a slider channel around itsperiphery, a linear slider, a dial, etc.) includes tick marks 9020 thatprovide markers of unit of time along or around the sleep time adjusterobject 9036. In some embodiments, the sleep duration indicator 9022changes one or more characteristics of its appearance in accordance withthe duration specified by the first object 9024 and second object 9026,and/or by the bedtime indicator 9014 (if adjustable by user input) andwake time indicator 9016 (if adjustable by user input).

In some embodiments, described in additional detail with reference toFIGS. 9C-9I below, a first display property (e.g., color, pattern,thickness, shape, luminance, opacity, and/or saturation, etc.) of thesleep duration indicator 9022 is displayed at a first value when thecurrently specified sleep duration is above a preset threshold duration(e.g., the sleep goal previously specified in the sleep goal userinterface 9001), and switches to a second value when the currentlyspecified sleep duration is below the preset threshold duration. In someembodiments, the change in the value of the first display property ofthe sleep duration indicator 9022 is a binary change that occurs whenthe threshold duration is crossed, and does not change further or changegradually (e.g., the value of the first display property remainsconstant) in accordance with further changes of the sleep duration aslong as the threshold duration is not crossed by the changing sleepduration. In some embodiments, the change in the value of the firstdisplay property is accompanied by a change in the sleep goal message9030 that textually indicates whether the threshold duration (e.g.,sleep goal) is met by the currently specified sleep period. In someembodiments, in addition to the binary change that occurs when thecurrently specified sleep duration crosses the threshold duration, thesleep duration indicator 9022 optionally has one or more other displayproperties whose values are adjusted (e.g., continuously or in aplurality of small steps, etc.) in accordance with the change in thesleep duration as specified by the user's inputs irrespective of whetherthe sleep duration is above or below the threshold duration. Forexample, in some embodiments, the length of the sleep duration indicator9022 changes continuously in accordance with the changes made to thetotal duration of the sleep period, irrespective of whether the durationof the sleep period as currently specified meets the specified sleepgoal, however, a selected first property (e.g., color) of the sleepduration indicator switches from a first value to a second value (orfrom the second value back to the first value) when the duration crossesthe specified sleep goal during an increase in sleep duration (or duringa decrease in sleep duration). In some embodiments, other first displayproperties include, for example, fill option/pattern (e.g., binaryvalues include solid vs. pattern, or cross hatches vs. grid),transparency (e.g., solid vs. 50% transparency), thickness (e.g., lxthickness vs. 2 x thickness, etc.), etc.

FIG. 9C illustrates a user interacting with the sleep schedule userinterface 9011. The user input by contact 9028 moves the first object9024 along the sleep time adjuster object 9036 (e.g., including theclock face 9018 and slider channel around the clock face), from 10:30 PMto 11:00 PM. The bedtime indicator 9014 is updated to show the adjustedstart time of the sleep period. Since the pre-established sleep goal inthis example is 8.5 hours, as soon as the sleep duration falls below thepre-established sleep goal, the first display property (e.g., color,fill option/pattern, etc.) of the sleep duration indicator 9022 switchesfrom a first value (e.g., gray, solid filled, etc.) to a second value(e.g., red, pattern filled, etc.). In the state shown in FIG. 9C, theduration of the sleep period (e.g., 8 hours) is below thepre-established sleep goal of 8.5 hours, and the sleep durationindicator 9022 maintains the second value (e.g., red, pattern filled,etc.) for the first display property. FIG. 9D shows that, as the userinput by contact 9028 continues to adjust the position of the firstobject 9024 along or around the sleep time adjuster object 9036, from11:00 PM to 12:00 AM, the sleep duration has now dropped to 7 hours,remaining below the pre-established sleep goal of 8.5 hours. As aresult, the value of the first display property (e.g., color, filloption/pattern, etc.) remains unchanged from that shown in FIG. 9C wherethe sleep duration was 8 hours and also below the sleep goal. FIG. 9Eillustrates a user input by the contact 9028 moving the first object9024 along or around the sleep time adjuster object 9036, (e.g., in adirection opposite the direction shown in FIGS. 9C and 9D). In the stateshown in FIG. 9E, the sleep period is from 12:30 AM to 7:00 AM, givingrise to a sleep duration of 6.5 hours, still below the pre-establishedsleep goal of 8.5 hours; and accordingly, the first display property(e.g., color, pattern filled, etc.) of the sleep duration indicator 9022is maintained at the second value (e.g., red, pattern filled, etc.).

FIG. 9F shows that the first object 9024 has been moved by the userinput along or around the sleep time adjuster object 9036, from alocation corresponding to 12:30 AM to a location corresponding to 10:00PM. Accordingly, the bedtime indicator 9014 displays the adjustedstarted time as 10:00 PM and the sleep duration is adjusted to 9 hours.Since 9 hours is greater than the pre-established sleep goal of 8.5hours, the sleep duration indicator 9022 is displayed with the firstdisplay property at the first value (e.g., the same value as the firstdisplay property of the sleep duration indicator 9022 in FIG. 9B). Thevalue change (e.g., switching from the second value to the first value)for the first display property (e.g., color, fill option/pattern, etc.)of the sleep duration indicator 9022 occurs when the first object 9024is dragged across the location along or around the periphery of theclock face 9018 that corresponds to 10:30 PM.

FIG. 9G illustrates that a user input by a contact 9038 can drag thesecond object 9026 in a clockwise direction along or around the sleeptime adjuster object 9036, from 7:00 AM to 7:30 AM, increasing the sleepduration from 9 hours to 9.5 hours. Since the sleep duration remainsabove the pre-established sleep goal of 8.5 hours, the first displayproperty (e.g., color, fill pattern) of the sleep duration indicatorremains unchanged at the first value (e.g., gray, solid filled, etc.)(e.g., same as the state shown in FIGS. 9F and 9B).

FIG. 9H illustrates that a user input by the contact 9038 can drag thesecond object 9026 in a counterclockwise direction along or around thesleep time adjuster object 9036, from 7:30 AM to 6:00 AM, decreasing thesleep duration from 9.5 hours to 8 hours. Since the sleep durationdecreases from above the pre-established sleep goal to below thepre-established sleep goal, the value of the first display property ofthe sleep duration indicator 9022 switches from the first value to thesecond value when the second object is dragged passed the locationcorresponding to 6:30 AM toward 6:00 AM and remain at the second valueduring the further changes to the wake time made in accordance with thedrag input.

FIG. 9I illustrates a user input by the contact 9038 can drag the secondobject 9026 in the clockwise direction again along or around the sleeptime adjuster object 9036, from 6:00 AM to 6:30 AM, increasing the sleepduration from 8 hours to 8.5 hours. Since the sleep duration reaches thepre-established sleep goal from below the sleep goal, the value of thefirst display property of the sleep duration indicator 9022 switchesfrom the second value (e.g., red, pattern filled, etc.) back to thefirst value (e.g., gray, solid filled, etc.) when the second objectreached the location corresponding to 6:30 AM.

FIGS. 9B-9I illustrate the sleep time adjuster object 9036 changing itsappearance to indicate whether a sleep goal is met by the currentlyspecified sleep period in a sleep schedule user interface 9011 forsetting up a sleep schedule (e.g., sleep schedule 1) that optionallyapply to multiple days (e.g., all weekdays). In some embodiments, themultifunction device 100 allows the user to only adjust the sleepschedule for an upcoming sleep period of an existing sleep schedule(e.g., for the current day). FIGS. 9J-9P illustrate exemplary userinterfaces for editing the sleep period for an upcoming sleep period(e.g., during a wind down period), or using an alarm application.

FIG. 9J illustrates an exemplary sleep screen 5083 that is displayedwhen the device is woken at a time during the sleep period of an activesleep schedule, in accordance with some embodiments. In someembodiments, the sleep screen 5083 includes an alarm affordance 5086that specifies the schedule wake time. In some embodiments, the winddown screen includes a similar alarm affordance 5086 if no applicationactions have been set up for the wind down screen 5013. In someembodiments, the alarm affordance 5054 is included in the action platter5047 along with shortcuts for application functions, displayed (FIG. 5K)on the wind down screen 5013 or the sleep screen 5083. In someembodiments, the alarm affordances 5086 and/or 5054 can be activated(e.g., by a user input by a contact 5084), and in response an alarmapplication user interface 9041 is displayed (FIG. 9K) through whichsleep time for the upcoming sleep period can be adjusted before thearrival of the sleep period.

In FIG. 9K, the computer system displays the alarm application userinterface 9041 in accordance with some embodiments. The alarmapplication user interface 9041 includes a first portion (e.g., a toprow) that displays the start time and the end time of the upcomingscheduled sleep period and an indication of a type of notification to bepresented at the end time of the upcoming scheduled sleep period (e.g.,whether wake alarm is set or not set). In some embodiments, the alarmapplication user interface 9041 includes a link 9048 that, whenactivated (e.g., by a tap input by a contact 9050), causes display ofsleep time adjusting user interface 9051 through which the upcomingsleep period (e.g., tonight only) can be modified. In some embodiments,activating the link 9048 causes display of the sleep schedule userinterface 9011 through which the entire sleep schedule (e.g., sleepschedule 1) including the upcoming sleep period can be modified. In someembodiments, the alarm application user interface 9041 includes one ormore additional alarms (e.g., a scheduled alarm 9042) that have been setto go off (e.g., recurring alarm that goes off at 2:30 AM everyWednesday, etc.) in addition to the wake alarm of the upcoming sleepperiod of the multifunction device 100.

FIG. 9L illustrates an exemplary sleep time adjusting user interface9051 through which the upcoming sleep period (e.g., tonight only) can bemodified. In some embodiments, as shown in FIG. 9L, the sleep timeadjusting user interface 9051 includes the sleep time adjuster object9036 is for adjusting the start time and the end time of the sleepperiod that applies to the current day (e.g., through the same methodsas described with reference to FIGS. 9A-9I). In such embodiments, thesleep time adjusting user interface 9051 optionally includes a fullsleep schedule link 9052 for editing the whole sleep schedule to whichthe upcoming sleep period belongs (e.g., for future occurrences and notjust for the current day).

As shown in FIG. 9M, the bedtime is adjusted from 10:00 PM to 10:30 PM,while the wake time is adjusted from 6:30 AM to 7:00 AM, e.g., inresponse to two inputs by contact 9028 and 9038, respectively. As aresult of the adjustment, the whole sleep duration indicator 9022 isshifted along or around the sleep time adjuster object 9036, and thetotal length of the sleep duration indicator 9022 remains unchanged at8.5 hours. Since the total duration of the sleep period meets thepre-established sleep goal throughout the change, the first displayproperty (e.g., color, fill option/pattern, etc.) of the sleep durationindicator 9022 remains at the second value (e.g., gray, solid filled,etc.) from the start to the end of the inputs.

As shown in FIG. 9N, the bedtime is adjusted from 10:30 PM to 10:00 PM,while the wake time is adjusted from 6:30 AM to 7:00 AM, e.g., inresponse to two inputs by contact 9028 and 9038, respectively. As aresult of the adjustment, the total duration of the sleep perioddecreases below the pre-established sleep goal of 8.5 hours to 8 hours.Since the total duration of the sleep period does not meet thepre-established sleep goal the change, the first display property (e.g.,color, fill option/pattern, etc.) of the sleep duration indicator 9022switches from the second value (e.g., gray, solid filled, etc.) to thefirst value (red, pattern filled) at the time when the total durationfalls below the threshold duration of 8.5 hours. The change in the valueof the first display property is accompanied by a change in the sleepgoal message 9030 that textually indicates the threshold duration (e.g.,sleep goal) is not met by the currently specified sleep period.

In addition, in FIG. 9N, a tap input by a contact 9054 is detected onlink 9052 in the sleep time adjusting user interface 9051, and inresponse, as shown in FIG. 9O, the computer system displays the sleepschedule user interface 9011 that allows for editing the sleep schedulefor future occurrences and not just for the current day. In addition toadjusting the bedtime 9014 and/or wake time 9016, the user may add orremove days from the current schedule (e.g., sleep schedule 1) via theday selection region 9012 in the sleep schedule user interface 9051. InFIG. 9), the current sleep period applies to five weekdays, and a userinput by a contact 9056 is detected on an unselected day (e.g.,Saturday) in the day selection region 9012 to add it to the currentsleep schedule.

In some embodiments, in response to the modification to the currentsleep schedule (e.g., adding Saturday to the sleep schedule 1), themultifunction device 100 determines whether this modification conflictswith any existing sleep schedules. In accordance with a determinationthat adding Saturday to the current sleep schedule does conflict with anexisting sleep schedule (e.g., in this example, there is already a sleepschedule for Saturday), as shown in FIG. 9P, the multifunction device100 displays a conflict warning 9058 that the selected day (e.g.,Saturday, as selected by the user input 9056) already has a sleepschedule that has a different set of sleep schedule settings (e.g.,different bedtime, wake time, duration, sleep modes, etc.) from thecurrent sleep schedule (e.g., sleep schedule 1). In some embodiments,the conflict warning 9058 includes an affordance 9060 for confirmingthat the user wishes to override the existing schedule for the newlyadded day and proceed with the modification. In some embodiments, theconflict warning 9058 includes an affordance 9062 to cancel themodification and maintain the existing sleep schedule. In this example,an input by a contact 9064 on the cancel affordance 9062 is detected andthe newly selected day (e.g., Saturday) is not added to the currentsleep schedule (e.g., sleep schedule 1).

FIGS. 9Q-9AG illustrate exemplary user interfaces for setting up one ormore sleep schedules and related operation modes, respectively, using afirst computer system (e.g., a portable multifunction device 100) and asecond computer system (e.g., a peripheral device 700) to set up sleepschedules. For ease of discussion, the user interfaces for the firstcomputer system and the second computer system are described side byside through the set up process. In some embodiments, if the firstcomputer system and the second computer system are paired devices,setting up the schedule on one system also sets up the schedule for theother system. There is however, no requirement that sleep schedule setupon one computer system be dependent on the computer system having apaired companion system. Each computer system can independently supportits own sleep schedules as a standalone device. In some embodiments, thesecond computer system displays a subset, simplified version, ormodified version of the user interface displayed on the first computersystem. For ease of discussion, the first computer system will bedescribed as the portable multifunction device 100 and the secondcomputer system will be described as the peripheral device 700. In someembodiments, some of the user interfaces described in FIGS. 9Q-9AG arespecific to the portable multifunction device 100 or the peripheraldevice 700, but not both. In some embodiments, the first and secondcomputer systems display similar user interfaces, but presented in adifferent order (e.g., the portable multifunction device 100 displays awind down user interface later in the sequence of user interfaces at adifferent time (or in a different position in the sequence of userinterfaces) than the peripheral device 700).

FIG. 9Q illustrates exemplary sleep goal user interfaces in accordancewith some embodiments. The portable multifunction device 100 displays asleep goal user interface (e.g., the sleep goal user interface 9001shown in FIG. 9A). The peripheral device 700 displays a correspondingsleep goal user interface 9067. Both includes user interface objects forspecifying a duration of a sleep goal (e.g., affordances 9006 and 9070for decreasing the duration, and affordances 9008 and 9072 forincreasing the duration), in accordance with some embodiments. Both userinterfaces include affordance (e.g., “next” buttons 9010 and 9074) fornavigating to the next stage after the sleep goal is established.

FIGS. 9R-9S illustrate exemplary sleep schedule user interfaces forsetting up a first sleep schedule, in accordance with some embodiments.The portable multifunction device 100 displays a setup user interface9076 and the peripheral device 700 displays a setup user interface 9082.In some embodiments, the portable multifunction device 100 displaysbackground information (e.g., sleep schedule information 9077) while theperipheral device 700 does not display the background informationregarding sleep schedules. The user can continue with sleep schedulesetup (e.g., via either a setup button 9078 or a next button 9080 forthe portable multifunction device 100 using the sleep schedule userinterface 9093 as shown in FIG. 9S (e.g., selecting days using the dayselector 9012, and specifying the bedtime and wake time using the sleeptime adjuster object 9036, setting up wake alarm and snooze functionsusing control affordances 9032 and 9034, etc.). In FIG. 9R, theperipheral device 700 displays user interface object 9086 for specifyingthe wakeup time, a user interface object 9088 for setting a wake upalarm, a user interface object 9090 for specifying a bedtime, and anaffordance 9084 for navigating to the day selector user interface 9094(FIG. 9S). In the day selector user interface 9094, selectablerepresentations of days of the week are displayed in a day selector9096, and selected days are added to the sleep schedule. After thebedtime and wake time, and the days of the sleep schedule is set, theuser can navigate to the next stage of the set up process using the nextbutton 9092 or 9098. In some embodiments, as shown in FIG. 9S, theperipheral device 700 may display a subset, simplified version, ormodified version of the user interface displayed on the portablemultifunction device 100. For example, the portable multifunction device100 displays a (single) sleep schedule setup user interface 9093, whilethe peripheral device 700 displays both the setup user interface 9082(shown in FIG. 9R) and setup user interface 9094.

FIG. 9T illustrates exemplary schedule summary user interfaces 9100 and9112, which are displayed as the user continues with the sleep schedulesetup (e.g., via an add button 9095 for the portable multifunctiondevice 100, via a next button 9098 for the peripheral device 700). Forexample, the portable multifunction device 100 displays a first schedule9102 that displays the sleep period and alarm setting for the newlyadded first schedule, an edit button 9104 for editing the firstschedule, a missing days notification 9106 that, when activated,displays the days that currently do not have a schedule, and an addschedule button 9108 for setting up another schedule. The peripheraldevice 700 similarly displays a first schedule 9114 and an add schedulebutton 9116 in the schedule summary user interface 9112.

As shown in FIG. 9U, activating the add schedule button (e.g., addschedule button 9108, add schedule button 9116, FIG. 9T) causes displayof a sleep schedule user interface for a new schedule (e.g., sleepschedule user interface 9120 for the portable multifunction device 100,sleep schedule user interface 9122 for the peripheral device 700). Thesetup user interfaces are analogous to the setup user interfaces shownin FIGS. 9R and 9S. In this example, a new schedule is set up forSaturday, with a different set of bedtime and wake time, and differentalarm and snooze settings from the sleep schedule 1 that was set upearlier.

FIG. 9V illustrates the schedule summary user interface 9100 for theportable multifunction device 100 and schedule summary user interface9112 for the peripheral device 700 after an additional schedule (e.g.,as shown in FIG. 9T) has been added. The portable multifunction device100 displays the first schedule 9102 and a second schedule 9124 (e.g.,the new schedule set up in FIG. 9T). The peripheral device 700 similarlydisplays the first schedule 9114 and a second schedule 9128. The userinterface object corresponding to the first schedule 9114 and the secondschedule 9128 on the peripheral device, when activated, respectivelycause display of the sleep schedule interfaces corresponding to the twoschedules (e.g., sleep schedule user interface 9082 in FIG. 9R, sleepschedule user interface 9122 in FIG. 9U, respectively) where the sleepschedules can be edited. The edit buttons 9104 and 9126 displayed nextto the first schedule 9102 and the second schedule 9124 respectivelycause display of the sleep schedule user interfaces corresponding to thetwo schedules (e.g., sleep schedule user interface 9011 in FIG. 9I,sleep schedule user interface 9120 in FIG. 9U, respectively), whenactivated.

FIGS. 9W-9X illustrate that, in response to activation of the nextbutton 9110 or 9118 in FIG. 9V, exemplary user interfaces 9130 and 9150for setting up a sleep mode for the sleep period of current sleepschedule are displayed. The multifunction device 100 displays backgroundinformation 9132 and 9133 regarding the sleep mode, an enable button9134 for enabling the sleep mode, and a skip button 9136 for not settingup the sleep mode for the current sleep schedule. In some embodiments,the background information 9132 and additional background information9133 alternate periodically. In some embodiments, the peripheral device700 does not display additional background information regarding sleepmode, and sleep mode is automatically enabled for each sleep schedulethat has been setup.

FIG. 9Y illustrates exemplary user interface for setting up a wind downperiod before the sleep period on the portable multifunction device 100in accordance with some embodiments. FIGS. 9W-9X illustrate exemplaryuser interfaces for setting the wind down period before the sleep periodon the peripheral device 700, in accordance with some embodiments. Forexample, in response to the user enabling the sleep mode using theenable button 9134 in FIG. 9W or 9X, the portable multifunction device100 displays a wind down setup user interface 9158 which allows the userto set a wind down period 9132 (e.g., via minus button 9164 and plusbutton 9166) before the sleep period. The wind down period is enabled byactivation of the enable button 9168 or skipped by activation of theskip button 9170. In some embodiments, the wind down set up userinterface 9134 also includes background information 9160 about the winddown mode. In some embodiments, example wind down screens are shown inthe background information 9160.

FIGS. 9W-9X, the peripheral device 700 displays modified backgroundinformation 9139 about the wind down mode, a wind down period selector9140 for specifying a duration of the wind down period before each sleepperiod of the sleep schedule, an enable button 9146 for enabling thewind down mode for the wind down period, and a skip button 9148 for notenabling wind down mode for the sleep periods of the sleep schedule.FIGS. 9W-9X show the process for specifying a duration of the wind downperiod during which the wind down mode is active. The wind down periodcan be adjusted via minus button 9142 and plus button 9144.

In FIG. 9Y, once the wind down set up has been completed (e.g., enabledby Enable button 9146, or skipped by skip button 9148 in FIG. 9X), theperipheral device 700 displays a charge reminder setup user interface9172 (e.g., a device-specific user interface) that includes backgroundinformation 9174 and an enable button 9176. Once enabled, a batterycharge reminder and battery charge status will be generated on theperipheral device 700 and/or the companion multifunction device 100during the wind down period or other preset period before the sleepperiod (e.g., as described with respect to FIGS. 7A-7J, for example).

FIGS. 9Z-9AB illustrate a process for setting up a limited set ofapplication functions that are available on the wind down screen (e.g.,wind down screen 5013) and sleep screen (e.g., sleep screen 5083)without dismissing the wind down screen and sleep screen, in accordancewith some embodiments. In some embodiments, the portable multifunctiondevice 100 displays a different sequence of setup user interfaces thanthe device 700. In some embodiments, the portable multifunction device100 displays a set user interfaces specific to the portablemultifunction device 100, that are not displayed on the peripheraldevice 700. For example, the portable multifunction device 100 displaysshortcut setup user interfaces 9178, 9186, 9194, and 9198, that are notdisplayed on peripheral device 700 (e.g., because shortcut functionalityis available on the multifunction device 100 and not on the peripheraldevice 700). In FIG. 9Z, the user interface 9178 includes backgroundinformation 9180 about shortcuts that can be set up for the wind downscreen. In response to activation of the set-up button 9182, theportable multifunction device 100 displays shortcut setup user interface9186 which includes an add shortcut button 9188, as shown in FIG. 9Z. Inresponse to detecting a user input by a contact 9192 on the add shortcutbutton 9188 (FIG. 9Z), the portable multifunction device 100 displays ashortcut selection user interface 9194 (FIG. 9AA). For example, CalmMindapplication 5068, Wish application 5070, Notes application 5072, andMusic application 9195 are displayed in separate application categories.In some embodiments, one or more functions associated with a shortcutcan be selected for each application, such as an open applicationfunction 5074, or a start sleep meditation function 5076. In someembodiments, the shortcut selection user interface 9194 displays asubset of the available functions for a particular application bydefault. Additional functions may be displayed (e.g., by activating ashow more button 5078). In some embodiments, the displayed applicationsinclude recommended applications (e.g., applications curated from a listof all available applications with shortcut functions). Additionalapplications can be selected (e.g., via a “show more recommended apps”button 9196). FIG. 9AB illustrates the shortcut summary user interface9198 after an application function associated with the CalmMindapplication has been added. The CalmMind action shortcut 5068 isdisplayed in the shortcut setup user interface 9186. The user can addadditional shortcuts (e.g., via the “add another shortcut” button 9202).The shortcut setup user interface 9186 and the shortcut summary userinterface 9198 each includes a next button (e.g., 9190 in FIG. 9A, 9204in FIG. 9AB) that, when activated, navigates to the next stage of thesetup process.

In some embodiments, in response to activating the next button 9204 inFIG. 9AB, the portable multifunction device 100 displays a sleeptracking setup user interface 9208, in accordance with some embodiments.The sleep tracking setup user interface 9208 includes backgroundinformation 9210 about using a peripheral device 700 that is paired withthe multifunction device 100 to track sleep quality of the user, andenable button 9212 for enabling the sleep tracking function, and a“don't enable” button 9214 for not enabling the function.

FIG. 9AC illustrates exemplary setup summary user interfaces 9216 and9226, in accordance with some embodiments. The portable multifunctiondevice 100 displays a setup summary user interface 9216 that includes asleep goal section 9218, a first schedule section 9220, a secondschedule section 9222, and a feature section 9224. The peripheral device700 displays a setup summary user interface 9226 that includes a sleepgoal section 9228, a first schedule section 9230, a second schedulesection 9232, and a feature section 9234. The set up summary userinterfaces displays the sleep schedules that have been set up and theirassociated operation modes and functions. Selection of the done button9232 concludes the set up process on the peripheral device 700.

FIGS. 9AD-9AG illustrate example user interfaces of an application thatmanages the sleep schedule and related sleep data on a multifunctiondevice 100 and a peripheral device 700, in accordance with someembodiments.

FIG. 9AD illustrates exemplary sleep data user interfaces 9238 and 9248in accordance some embodiments. The portable multifunction device 100displays a sleep data user interface 9238 that includes historic sleepdata information (e.g., presented as a graph 9240); a current sleep goalindicator 9242 which, when activated, causes display of a user interfacefor editing the sleep goal (e.g., user interface 9001 in FIGS. 9A and9Q); an edit sleep schedule button 9244 that when activated displays asummary of existing sleep schedules (e.g., user interface 9474 in FIG.9AF, or user interface 9100 in 9V, etc.), and current scheduleinformation 9246 that includes sleep schedule that applies to thecurrent day. The peripheral device 700 displays a sleep data userinterface 9248 that includes historic sleep data information (e.g.,presented as a graph 9250), a current sleep goal indicator 9252, an editsleep schedule button 9254, and current schedule information 9256, thatfunction similarly to their counterparts in the user interface 9238shown on multifunction device 100. In some embodiments, the sleep datauser interface 9238 and sleep data user interface 9248 optionallydisplays visual indications regarding satisfaction of the sleep goal fora past sleep period and/or for a past sequence of days.

FIG. 9AE illustrates additional portions of the sleep data userinterfaces 9238 and 9248 after scrolling down. The sleep data userinterface 9238 of the portable multifunction device 100 displays secondschedule information 9258, data highlights 9260, and additional sleepresources (e.g., tips 9262 and 9264). The sleep data user interface 9248of the peripheral device 700 displays second schedule information 9470and data highlights 9472.

FIG. 9AF illustrates exemplary user interfaces 9474 and 9492 for editingsleep schedules that are accessible from within the sleep data userinterfaces 9238 and 9248 shown in FIGS. 9AD-9AE (e.g., via edit sleepschedule button 9244, via edit sleep schedule button 9254). The portablemultifunction device 100 displays a sleep schedule editing userinterface 9474 that includes a current schedule for an upcoming sleepperiod (e.g., schedule active for the current day) section 9476, a firstschedule (e.g., sleep schedule 1) section 9478, and a second schedule(e.g., sleep schedule 2) section 9478, each of which can be edited(e.g., via an edit affordance in the respective schedule section). Thesleep schedule editing user interface 9474 includes an “Add Another”button 9482 for displaying a user interface for adding additionalschedules, a sleep goal section 9486 for displaying the user interfacefor editing the current sleep goal, a shortcuts section 9488 fordisplaying the user interface for editing the set of applicationfunctions that are available on the wind down screen or sleep screen,and an options section 9490 for displaying settings for the sleep modesand related functions (e.g., sleep mode, wind down mode, good morningmode, alarm setting, snooze setting, sleep tracking, etc.). In someembodiments, each respective section is an affordance (e.g., a button)that can be activated to edit the respective function of the sleep mode(e.g., the sleep goal section 9484 can be activated to edit the sleepgoal duration). The peripheral device 700 displays a sleep scheduleediting user interface 9492 that includes current schedule (e.g.,schedule active for the current day) section 9494, a first schedule(e.g., sleep schedule 1) section 9496, and a second schedule (e.g.,sleep schedule 2) section 9498, each of which can be edited (e.g., viaan edit affordance in the respective schedule section). The sleepschedule editing user interface 9492 includes an “add another schedule”button 9500 to add additional schedules, a sleep goal section 9502, awind down toggle 9504 for turning on/off the wind down mode, a chargereminder toggle 9508 for turning on/off charge reminders, and a sleeptracking toggle 9506 for turning on/off sleep tracking.

FIG. 9AG illustrates an exemplary user interface for editing optionsassociated with a sleep schedule (e.g., displayed in response toactivating the options section 9490 in FIG. 9AF). The portablemultifunction device 100 displays an options user interface 9510 thatincludes toggles 9512-9522 for various functions associated with a sleepschedule. In some embodiments, the peripheral device 700 displays asubset of these toggles in the sleep schedule editing user interface9492 (e.g., the wind down toggle 9504, charge reminder toggle 9508, andsleep tracking toggle 9506 shown in FIG. 9AF). In FIG. 9AG, the sleepmode is enabled for the sleep periods of the active sleep schedules,which turns on Do Not Disturb mode and sleep screen functions during thesleep periods, and turns on the wind down screen during the wind downperiods preceding the sleep periods. The turn on automatically functionis enabled so that the sleep modes and related DND and special wakescreens are automatically turned on based on the current time beingwithin the schedule wind down period, sleep period, and wind up period.The show time function is enabled so that the sleep screen still showsthe current time. If the show time function is disabled, the sleepscreen only shows the current date. The use phone to track time in bedfunction is enabled such that sleep quality can be monitored (e.g.,activity on the device is tracked to determine if the user is followingthe sleep schedule) using a portable multifunction device (e.g., inaddition to the peripheral device or in the absence of the peripheraldevice). The sleep reminders function is enabled so that a notificationor reminder is generated right before the wind down starts andoptionally right before the sleep period starts. The sleep resultnotification function is enabled such that the user will receive asummary of last night's sleep in the morning via a notification. Thewatch section 9524 shows which, if any, peripheral devices have been setup as a companion device to implement some of the functions of the sleepmode, wind down mode, good morning mode, bedtime reminders, chargingreminders, sleep tracking, and sleep coaching, etc.

FIGS. 10A-10C are flowchart diagrams of a method 10000 of providing avisual alert when a duration of a sleep time period is adjusted by auser below an established sleep goal, in accordance with someembodiments.

This method relates to displaying either the first or the second visualindication that indicates whether a duration of a first scheduled sleepperiod meets a preset threshold duration (e.g., a pre-established sleepgoal) while adjusting the duration of the first scheduled sleep periodby changing a start time and/or end of the first scheduled sleep period,where the change in visual indication is performed when a sleep goalthreshold is crossed by the duration of the first scheduled sleepperiod. Displaying different visual indications based on the comparisonswith a preset sleep goal alerts the user that the adjustment to thesleep period may be contrary to the user's intent, and alert the user toprovide the required input to achieve an intended outcome. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The method 10000 is performed at a computer system (e.g., a handheldelectronic device, a mobile phone, a tablet device, a computer, awearable device, etc.) in communication with a display generationcomponent (e.g., a display, a touch-screen display, a projector, ahead-mounted display (HMD), etc.) and one or more input devices (e.g., atouch-sensitive surface (e.g., separate from a display or integrated ina touch-screen display), an accelerometer, a camera, a motion sensor,etc.). In the method 11000, the computer system displays (10002) a firstuser interface (e.g., a user interface displayed during the set upprocess for a sleep schedule for a particular day) for specifying asleep schedule, the first user interface including one or more userinterface objects (e.g., a linear slider, a circular slider, text inputfields, a dial, a clock face with movable hands, etc.) that areconfigured to receive user inputs that specify at least one of a starttime and an end time of a first scheduled sleep period for the sleepschedule (e.g., the first scheduled sleep period will be used for one ormore upcoming days). The computer system receives, via the first userinterface, a first user input that specifies a first time value thatspecifies at least one of the start time and the end time of the firstscheduled sleep period for the sleep schedule (e.g., a value for thestart time or end time of the scheduled sleep time for a particular day(e.g., Mondays, Tuesdays, Saturdays, Jun. 18, 2020, the current day, thenext day, etc.) that is being set up). In response to receiving thefirst user input (10006): in accordance with a determination that aduration of the first scheduled sleep period that is determined based onthe first time value is below a preset threshold duration (e.g., auser-specified sleep goal, a recommended sleep goal, etc.), the computersystem displays (10008) (e.g., on the first user interface andconcurrently with the one or more user interface objects that areconfigured to receive user inputs that specify at least one of the starttime and the end time of the first scheduled time period for the sleepschedule, on a user interface that displays a visual representation ofthe first scheduled time period, etc.) a first visual indication thatthe duration of the first scheduled time period is below the presetthreshold duration, wherein a first value is selected for a firstdisplay property (e.g., color, thickness, shape, luminance, opacity,and/or saturation etc.) of the first visual indication while theduration remains below the preset threshold duration (e.g., the firstvalue is independent of changes made to the duration of the firstscheduled time period in response to user inputs, as long as theduration remains below the preset threshold duration); and in accordancewith a determination that the duration of the first scheduled timeperiod that is determined based on the first time value is at or abovethe preset threshold duration (e.g., a user-specified sleep goal, arecommended sleep goal, etc.), the computer system displays (10010)(e.g., on the first user interface and concurrently with the one or moreuser interface objects that are configured to receive user inputs thatspecify at least one of the start time and the end time of the firstscheduled time period for the sleep schedule, on a user interface thatdisplays a visual representation of the first scheduled time period,etc.), a second visual indication that the duration of the firstscheduled time period is meets the preset threshold duration, wherein asecond value, different from the first value, is selected for the firstdisplay property (e.g., color, thickness, shape, luminance, opacity,and/or saturation etc.) of the second visual indication while theduration remains at or above the preset threshold duration (e.g., thesecond value is independent of changes made to the duration of the firstscheduled time period in response to user inputs, as long as theduration remains at or above the preset threshold duration). In someembodiments, when setting up a sleep schedule, the computer systemallows the user to enable a wind down period that precede the sleepperiod specified by the user. In some embodiments, the computer systemautomatically enters into a special mode that promotes reduced useractivity on the computer system and/or reduce distractions caused by thecomputer system. For example, during the wind down period and the sleepperiod, the Do Not Disturb mode is turned on, so that most of thenotifications are suppressed (e.g., except alarms, and sleep relatednotifications, etc.). In addition, in some embodiments, the wind downscreen and sleep screen that correspond to the screen-restricted stateof the computer system requires a special gesture to be dismissed, andwhen they are dismissed, the normal wake screen is displayed. In someembodiments, the wind down screen has a reduced number of user interfaceobjects and allow access to a limited set of application functions thatare preselected by the user, without dismissing the wind down screen. Insome embodiments, the sleep screen has even fewer user interface objectsthan the wind down screen, to further reduce the distractions to theuser during sleep. In some embodiments, during a set up process for thesleep schedule, the configuration user interface for the sleep mode hasoptions to set a duration for the wind down mode that startsautomatically before goodnight mode. In some embodiments, theconfiguration user interface also includes user interface objects forselecting the set of actions that are available on the wind down screenduring the wind down, and optionally, on the sleep screen during thesleep mode. In some embodiments, the set of actions that are availableinclude one or more system recommended application functions. In someembodiments, the configuration user interface provides a listing ofrecommended application actions for inclusion in the limited set ofactions to be displayed on the wind down screen and/or sleep screen. Insome embodiments, the set of available actions are filtered by appsinstalled on device. In some embodiments, the configuration userinterface provides a listing of applications installed on the devicethat have action shortcuts and this allows the user to browse foractions from the list of applications on the device. In someembodiments, if an application has multiple actions, selecting theapplication in the listing shows a list of actions available to beselected for the application. If an application has only a singleaction, then selection of the application adds the application to theset of actions for the wind down screen and/or sleep screen.

In some embodiments, the first user interface includes (10012) one ormore user interface objects that are configured to receive user inputsthat specify one or more days corresponding to the first scheduled sleepperiod. In the method 10000: the computer system receives (10012) asecond user input, via the first user interface, selecting a pluralityof days for the first scheduled sleep period, wherein the firstscheduled sleep period for the sleep schedule is applied (repeated) foreach day of the selected plurality of days. For example, in someembodiments, the first scheduled sleep period has a start time of 10:00PM and an end time of 8:30 AM, and the second user input selects thefive weekdays to be associated with the first schedule sleep period inthe sleep schedule, and the sleep mode is set up to be activated between10:00 PM till 8:30 AM on each of the selected weekdays. This is shown inFIG. 9B, for example, where the first user interface (e.g., the sleepschedule user interface 9011) is configured to receive user inputs thatspecify one or more days corresponding to the first scheduled sleepperiod (e.g., via the day selection region 9012). Selecting theplurality of days for the first scheduled sleep period in response tothe second user input reduces the number of inputs needed to perform anoperation (e.g., applying the first scheduled sleep period to multipledays). Reducing the number of inputs needed to perform an operationenhances the operability of the device, and makes the user-deviceinterface more efficient, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the computer system displays (10014) in a seconduser interface for modifying the first scheduled sleep period for arespective day of the selected plurality of days, wherein the seconduser interface includes one or more user interface objects (e.g., alinear slider, a circular slider, text input fields, a dial, a clockface with movable hands, etc.) that are configured to receive userinputs that specify at least one of the start time and the end time ofthe first scheduled sleep period for the respective day (e.g., themodified first scheduled sleep period will be used for the current dayonly). The computer system receives, via the first user interface, athird user input that specifies a second time value, different from thefirst time value, that specifies at least one of the start time and theend time of the first scheduled sleep period for the respective day. Inresponse to receiving the third user input, the computer system modifiesthe first scheduled sleep period for the respective day of the selectedplurality of days in accordance with the second time value, withoutmodifying the first scheduled sleep period for other days of theselected plurality of days. In some embodiments, the second userinterface also displays the visual indication that informs the userwhether the modified sleep period meets the preset threshold duration.In some embodiments, in response to the third user input: in accordancewith a determination that a duration of the modified first scheduledsleep period that is determined based on the second time value is belowthe preset threshold duration (e.g., a user-specified sleep goal, arecommended sleep goal, etc.), the computer system displays (e.g., onthe second user interface and concurrently with the one or more userinterface objects that are configured to receive user inputs thatspecify at least one of the start time and the end time of the firstscheduled time period for the respective day, on a user interface thatdisplays a visual representation of the first scheduled time period,etc.) the first visual indication that the duration of the modifiedfirst scheduled time period for the respective day is below the presetthreshold duration, wherein the first value is selected for the firstdisplay property (e.g., color, thickness, shape, luminance, opacity,and/or saturation etc.) of the first visual indication while theduration remains below the preset threshold duration (e.g., the firstvalue is independent of changes made to the duration of the firstscheduled time period in response to user inputs, as long as theduration remains below the preset threshold duration); and in accordancewith a determination that the duration of the modified first scheduledtime period that is determined based on the second time value is at orabove the preset threshold duration (e.g., a user-specified sleep goal,a recommended sleep goal, etc.), the computer system displays (e.g., onthe second user interface and concurrently with the one or more userinterface objects that are configured to receive user inputs thatspecify at least one of the start time and the end time of the firstscheduled time period for the respective day, on a user interface thatdisplays a visual representation of the modified first scheduled timeperiod, etc.), the second visual indication that the duration of themodified first scheduled time period meets the preset thresholdduration, wherein the second value, different from the first value, isselected for the first display property (e.g., color, thickness, shape,luminance, opacity, and/or saturation etc.) of the second visualindication while the duration remains at or above the preset thresholdduration (e.g., the second value is independent of changes made to theduration of the first scheduled time period in response to user inputs,as long as the duration remains at or above the preset thresholdduration). In some embodiments, the computer system further displaysanother visual indication that the proposed modification conflicts withan existing schedule (e.g., a sleep schedule for a different day, oranother non-sleep related schedule, etc.). In some embodiments, if auser input corresponds to a request to establish a new sleep schedulefor a respective day, and the computer system determines that therespective day already has an existing sleep schedule, the computersystem generates a warning that the respective day already has anexisting sleep schedule and requests the user to confirm that the userwishes to proceed with establishing the new sleep schedule for therespective day and override the existing schedule for the respectiveday. This is shown in FIG. 9U, for example, where the second userinterface (e.g., the sleep schedule user interface 9120) modifies thefirst scheduled sleep period for a respective day (e.g., Saturday, asselected in the day selection region 9012) of the selected plurality ofdays. Modifying the first scheduled sleep period for the respective dayof the selected plurality of days in accordance with the second timevalue and in response to receiving the third user input, withoutmodifying the first scheduled sleep period for other days of theselected plurality of days, performs an operation when a set ofconditions has been met without requiring further user input. Performingan operation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system is (10016) a first electronicdevice (e.g., the portable electronic device, such as a mobile phone ortablet device) that is communicatively coupled with (e.g., paired with,connected with, etc.) a second electronic device (e.g., a companiondevice such as a watch or bracelet, etc.). In the method 10000: inaccordance with a determination that a current time matches (e.g., is ator within a preset threshold amount of time of) the end time of thefirst scheduled sleep period for the sleep schedule, the computer systemprovides a first alert (e.g., a first notification, a first tactileoutput, a first audio alert, etc.) at the first electronic device (e.g.,the mobile phone or tablet device) a preset amount of time (e.g., 10seconds, 20 seconds, etc.) after a second alert is provided at thesecond electronic device (e.g., watch). This is shown in FIGS. 7H-7I,for example, where the first alert is provided at the first electronicdevice (e.g., the portable multifunction device 100, as shown in FIG.7I) after the second alert is provided at the second electronic device(e.g., the peripheral device 700, as shown in FIG. 7H). Providing thefirst alert at the first electronic device after providing the secondalert at the second electronic device, in accordance with adetermination that the current time matches the end time of the firstscheduled sleep period, performs an operation when a set of conditionshas been met without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system displays (10018) a second userinterface (e.g., user interface of an alarm app) that includes a firstportion (e.g., top row) that displays: the start time and the end timeof the first scheduled sleep period; and an indication of a type ofnotification to be presented at the end time of the first scheduledsleep period (e.g., silenced or alarm on). This is shown in FIG. 9T, forexample, where the second user interface (e.g., the schedule summaryuser interface 9100) includes a first portion that displays the starttime and the end time of the first scheduled sleep period (e.g., thefirst schedule 9102) and an indication of a type of notification to bepresented at the end time of the first scheduled sleep period. In someembodiments, the second user interface includes one or more additionalalarms that have been established for the computer system. In someembodiments, the second user interface includes a link that, whenactivated, causes display of the first user interface through which thesleep schedule can be modified, or display of the second user interfacethrough which the sleep period can be modified for a particular day(e.g., the current day only). Displaying the second user interface thatincludes the first portion that displays the start time and end time ofthe first scheduled sleep period, together with the indication of thetype of notification to be presented at the end of time of the firstscheduled sleep period, provides improved visual feedback to the user(e.g., allowing the user see the alarm type and alarm time from a singleuser interface). Providing improved visual feedback enhances theoperability of the device and makes the user-device interface moreefficient, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the sleep schedule includes (10020) the firstscheduled sleep period and a second scheduled sleep period; the firstscheduled sleep period is applied to a first set of days of a week(e.g., weekdays); and the second scheduled sleep period is applied toone or more days of the week (e.g., Saturday) that is not included inthe first set of days of the week; and the second user interfacedisplays: a start time and an end time of the second scheduled sleepperiod; and an indication of a type of notification to be presented atthe end time of the second scheduled sleep period. In some embodiments,the second user interface also displays an indication of the respectivedays of the week for the respective sleep schedules. This is shown inFIG. 9V, for example, where the second user interface (e.g., theschedule summary user interface 9100) includes the first scheduled sleepperiod (e.g., the first schedule 9102) applied to a first set of days ofa week (e.g., weekdays) and the second scheduled sleep period (e.g., thesecond schedule 9124) applied to one or more days of the week that arenot included in the first set of days of the week (e.g., Saturday).Displaying the second user interface that includes the start time andend time of the second scheduled sleep period, together with theindication of the type of notification to be presented at the end oftime of the second scheduled sleep period, provides improved visualfeedback to the user. Providing improved visual feedback enhances theoperability of the device and makes the user-device interface moreefficient, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, after the first scheduled sleep period for arespective day of the sleep schedule has ended, the computer systemdetermines (10022) whether an actual sleep duration of a user (e.g., asmonitored by using the watch) meets the preset threshold duration (e.g.,meets or exceeds the sleep goal). In accordance with a determinationthat the actual sleep duration of the user meets the preset thresholdduration, the computer system displays (e.g., within a second predefinedtime period after the end time of the first scheduled sleep period ofthe respective day) a third visual indication regarding satisfaction ofthe preset threshold duration. In accordance with a determination thatthe actual sleep duration of the user does not meet the preset thresholdduration, the computer system forgoes displaying a fourth visualindication regarding failure to meet the preset threshold duration(e.g., within the second predefined time period after the end time ofthe first scheduled sleep period). This is shown in FIG. 7J, forexample, where in accordance with a determination that the actual sleepduration of the user (e.g., 8 hours and 31 minutes) meets the presetthreshold duration (e.g., 8 hours and 30 minutes), the computer systemdisplays a third visual indication regarding satisfaction of the presetthreshold duration (e.g., the summary 7041). Displaying the third visualindication or the fourth visual indication, depending on whether theactual sleep duration of the user meets the preset threshold duration,performs an operation when a set of conditions has been met withoutrequiring further user input. Performing an operation when a set ofconditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

FIGS. 11A-11AF illustrate example user interfaces for disabling andenabling an input mechanism of an electronic device during a scheduledrestricted mode (e.g., a scheduled sleep time period), in accordancewith some embodiments.

FIGS. 11A-11AF are illustrated using a peripheral device 700, howeverthe process can be implemented using other types of computer systems,such as a multifunction device 100, a desktop computer, etc. In thisexample, device 700 is configured to operate in a normal mode (e.g.,normal display-on state) and a low-power mode (e.g., operated with adisplay-off state or an always-on low power state, etc.). In addition,the device 700 also operates in a restricted mode where the screen islocked by a screen-lock user interface (e.g., a lock screen or wakescreen in either the authenticated state or the unauthenticated state)so that access to the home screen and application user interfaces ofinstalled applications are prevented until the screen-lock userinterface is dismissed in response to user input. Furthermore, in someembodiments, the device 700 operates in a scheduled restricted mode(e.g., wind down mode, or sleep mode) during a preset scheduled timeperiod (e.g., a wind down period, or sleep period), where one or moreinput mechanisms that are normally enabled during a regular restrictedmode (e.g., when outside of the wind down period, or sleep period, andwhen a regular lock screen or wake screen can be displayed) are disabledin the scheduled restricted mode. As described herein, one or more inputmechanisms that are enabled outside of a scheduled restricted mode aredisabled during the scheduled restricted mode, and a predefined inputusing an enabled input mechanism is required to enable the disabledinput mechanisms during the scheduled restricted mode.

FIGS. 11A-11H illustrate exemplary user interfaces for interacting withthe device 700 when the device 700 is in a normal mode of operationoutside of scheduled mode change (e.g., outside of a sleep period orwind down period, etc.). More specifically, FIGS. 11A-11H illustrate oneor more input mechanisms of the device 700 that are enabled foroperating in a normal manner.

FIG. 11A illustrates the device 700 in a low power mode (e.g.,display-off state, or an always-on low power state). For example, in thelow power state, the device 700 is still on and detecting input via theone or more input mechanisms, but the touch screen 712 is notilluminated or activated (or is in a dimmed, low-power always-on state).In some embodiment, the device 700 enters the low power state when auser presses a lock button (e.g., input mechanism 7002 on the device700) or when the device 700 remains idle for a predefined amount of time(e.g., 30 seconds or a minute without the device 700 detecting an inputthat prevents the device 700 from entering the low-power state, such asa user input to perform operations on the device 700, or a wake input,described in further detail below).

FIG. 11A illustrates a number of inputs detected via various inputmechanisms of the device 700 that causes the device 700 to transitionfrom the low-power state to a normal operation state (e.g., with itsdisplay turned on, and/or lit-up from the low power always-on state tothe normal display-on state), in accordance with some embodiments. Anyone of these various wake inputs may be used independently to exit thelow power always-on state or the display-off state of the device 700when the current time is outside of the scheduled mode change (e.g., thesleep period). In some embodiments, the wake input is a tap or swipeinput by a contact 11002 on the touch screen 712 of the device 700. Insome embodiments, the wake input is a device raise input 11004 thatmoves the device 700 toward the user's face. In some embodiments, thewake input is actuation of a physical mechanism of the device 700. Forexample, the device 700 may include a rotatable input mechanism (e.g., awatch crown, a watch bezel, etc.), such as the input mechanism 7002 ofdevice 700, and the wake input is an input 11006 that rotates the inputmechanism 7002. In some embodiments, the device 700 includes a physicalmechanism that includes a button (e.g., a mechanical button, solid statebutton, etc.), a switch, or toggle, etc. For example, the device 700includes a side button 7004 configured to receive a press input 11008.In some embodiments, some of the physical mechanisms of the device 700are configured to receive multiple types of inputs. For example, theinput mechanism 7002 is a watch crown configured to receive both arotation input and a press input (e.g., of a button on the flat surfaceof the crown, depressed in a similar manner to the button 7004). In someembodiments, when an input mechanism is enabled and operating in anormal mode outside of the scheduled mode change, variouscharacteristics of the input (e.g., location, speed, direction,duration, number of occurrences, sequence, termination, etc.) are usedto disambiguate the inputs for triggering different operations. In someembodiments, at least some of the input mechanisms are disabled duringthe scheduled mode change (e.g., during the sleep mode enabled for thesleep period), and as a result, even if an input is detected, the device700 does not perform the normal input disambiguation based on thevarious characteristics of the input, and merely treats different typesof inputs as a signal that some interaction with the input mechanism hasoccurred and optionally ignores the input or displays an alert notifyingthe user that the input mechanism is disabled and/or what is required tore-enable the input mechanism.

FIG. 11B illustrates an initial user interface 11010 a that is displayedafter the device 700 exits the low power state (e.g., the display-offstate, or low-power always-on state, etc.), in response to detecting oneof the wake inputs described in FIG. 11A, and in accordance with adetermination that the current time is outside of the scheduled modechange (e.g., the scheduled sleep period). In some embodiments, the userinterface 11010 a includes a watch face (e.g., or another initial userinterface that the user has preconfigured as the regular wake screen orwind down screen (e.g., if the current time is within the wind downperiod) for the device 700).

In FIG. 11C, in response to an input 11012 on the input mechanism 7002of device 700, and in accordance with a determination that the currenttime is outside of the scheduled mode change (e.g., the scheduled sleepperiod), the device 100 displays a user interface 11014 (e.g., dismissesthe user interface 11010 a, or another regular wake screen, or the winddown screen), as shown in FIG. 11D. In some embodiments, the userinterface 11014 is a home screen and displays various applications thatcan be run on the device 700. In some embodiments, the additional input11012 is the same type of input as the input 11006. In some embodiments,the additional input 11012 is a different type of input from the input11006. For example, the input mechanism 7002 is a watch crown (e.g.,configured to rotate) and includes a physical button (e.g., on the flatsurface of the crown), and the input 11006 is a rotation of the inputmechanism 7002 (e.g., to wake the device 700), while the additionalinput 11012 is a press input on the physical button of the inputmechanism 7002.

In FIG. 11E, in response to an upward swipe input by a contact 11018 onthe touch screen 712 while the user interface 11010 a is displayed, thedevice 700 displays a settings user interface 11014 for configuringvarious device functions (e.g., network connections, alarms, camera, DNDmode, battery management, etc.) of the device 700, as shown in FIG. 11F.

FIG. 11G is analogous to FIG. 11E, but illustrates an additionaldownward swipe input by a contact 11020 on the touch screen 712 ofdevice 700. In response to the downward swipe input, the device 700dismisses the user interface 11010 a and displays a user interface11022, illustrated in FIG. 11H, that displays missed notifications. Insome embodiments, the user interface 11020 allows a user to interactwith (e.g., reply to) a notification (e.g., by tapping on a reply button11024 for a notification of a message on the touch screen 712).

Additional interactions with the device 700 are enabled using thevarious input mechanisms of the device 700 while the current time isoutside of the sleep period and all of the input mechanisms are enabled.

FIGS. 11I-11M illustrate the operations of the device 700 when thedevice 700 first enters the scheduled mode change (e.g., the sleep mode,with DND turned on and screen turned off or shown with simplified userinterface and reduced luminance, etc.). In some embodiments, the device700 disables at least some of the input mechanisms while in the sleepperiod of the active sleep schedule.

In FIG. 11I, a bedtime reminder user interface 11026 is displayed whenthe current time is one minute before the scheduled sleep period isstarted. For example, a user has scheduled a sleep time period beginningat 10:00 PM and ending at 6:30 AM. At 9:59 PM, the device 700 displaysthe bedtime reminder user interface 11026, which includes a “Sleep Well”message 11028, an alarm indicator 11030, and a dismiss button 11032.After bedtime reminder user interface 11026 is dismissed by a tap inputon the dismiss button 11032, the device 700 enters the sleep mode, wherea sleep screen is displayed and DND function is turned on, and one ormore input mechanisms of the device 700 are disabled.

FIG. 11J illustrates a sleep screen 11034 of the device 700 when thedevice 700 after the device has entered the sleep mode and before thedevice 700 enters into the low-power mode. In some embodiments, thesleep screen 11034 optionally displays a digital clock (e.g., as opposedto the watch face 11010 a) and an alarm status 11036 for the sleepperiod. In some embodiments, the sleep screen 11034 displays a DNDindicator 11040 indicating that the DND mode has been started. In someembodiments, the display is dimmer when displaying the sleep screen11034 than when displaying the bedtime reminder user interface 11026 anddisplaying the regular wake screen 11010 a of the device 700.

FIG. 11K illustrates a dark sleep screen 11038 that is displayed withthe device 700 has entered into a low power state during the scheduledsleep period. In some embodiments, the dark sleep screen 11038 isdisplayed after a preset period (e.g. 30 seconds, 1 minute, etc.) offollowing display of the sleep screen 11034. In some embodiments, thedark sleep screen 11038 is a completely off state, where the touchscreen 712 is not illuminated or active. In some embodiments, the darksleep screen 11038 is in the low-power always-on state, not displayingany time information or user interface objects, except for the DNDindicator 11040. In some embodiments, the display 712 displaying thedark sleep screen 11038 is even dimmer than the sleep screen 11034 shownin FIG. 11J.

As shown in FIG. 11K, while the current time is during the sleep periodand the device is operating in the sleep mode, with the display in thelow-power mode, the device 700 has disabled a number of inputmechanisms, including the touch-screen 712, the motion sensors to detectraising of the device, and the button 7004. In some embodiments, thepress button on the input mechanism 7002 is also disabled. For example,the device 100 does not respond to any input detected on the disabledinput mechanisms and/or treats different types of inputs that arenormally differentiated using the disabled input mechanisms as the sametype of input that triggers a fixed response. In some embodiments, thetouch-sensitive display 712 wakes to the sleep screen 11034 (as shown inFIG. 11L) from the dark sleep screen 11038 (as shown in FIG. 11K) inresponse to any of the user inputs that normally wakes the device fromthe lower-power mode outside of the scheduled sleep period (e.g., tapinput or swipe input by the contact 11002, raise input 11004, rotate (orpress) input 11006, or press input 11008) and then returns to the darksleep screen 11038 after a brief period of time. In some embodiments,the dark sleep screen 11034 remains unresponsive in response to userinputs (e.g., types of inputs for interacting with a regular wake screen11010 a as described in FIGS. 11C-11H) as long as the device 700 remainsin the sleep mode, as shown in FIG. 11N (e.g., showing the dark sleepscreen being maintained despite of the user inputs) following FIG. 11M(e.g., showing various inputs 11002, 11004, 11006, and 11008 that aredetected when the dark sleep screen 11034 is displayed). In someembodiments, the touch screen 712 does not wake in response to any userinput after the device 700 transitions to and remains in the sleep mode(e.g., once the dark sleep screen 11038 is displayed or once the screenis completely turned off). In some embodiments, repeated detection ofthe usual wake inputs cause the device 700 to transition from the darksleep screen 11038 to the sleep screen 11042, or from a completely darkscreen to the dark sleep screen 11038, during the sleep period.

FIGS. 11O-11T illustrate how to cause the device 700 to re-enable thedisabled input mechanisms during the sleep mode (e.g., without exitingthe sleep mode during the sleep period) in accordance with someembodiments. In some embodiments, a user input that meets a set of oneor more predefined criteria allows the user to exit the mode where oneor more input mechanisms are disabled. In some embodiments, the set ofone or more predefined criteria (e.g., criteria that prevent accidentalactivation of the device 700) includes a requirement for acharacteristic movement (e.g., rotation in a first direction by a firstthreshold number of turns, pressing consecutively a threshold number oftimes, etc.) of an input mechanism (e.g., a watch crown, a button, etc.)that is not disabled during the sleep mode. In some embodiments, thedevice 700 automatically re-enables the disabled input mechanisms oncethe end of the scheduled mode changes is reached (e.g., the end of thescheduled sleep time period is reached).

FIG. 11O illustrates that, while the dark sleep screen 11038 isdisplayed and the device 700 has disabled a plurality of inputmechanisms that are normally used to wake the device and navigate pastthe wake screen user interface (e.g., the touch-screen 712, the buttons7004 and press input on digital crown 11044 a, etc.), in response to aninitial input that is detected on the input mechanism that is notdisabled during the sleep mode, the device 700 displays an instructionuser interface 11046 in accordance with a determination that the inputreceived by the input mechanisms that is not disabled during the sleepmode meets prompt criteria (e.g., turned in the correct direction,turned at least once, etc.) but not the criteria for enabling thedisabled input mechanisms (e.g., but not enough number of turns, notfast enough, etc.). For example, in response to an initial portion 11044a of an input detected on the input mechanism 7002 that includes apartial rotation, or a rotation of one turn (as shown in FIG. 11O), thedevice 700 displays a prompt asking the user to keep turning the digitalcrown to exit the sleep mode (e.g., temporarily exit the sleep mode andre-enable the disabled input mechanisms before returning to the sleepmode, or terminate the sleep mode and re-enabled the disabled inputmechanisms, etc.), as shown in FIG. 11P. The instruction user interface11046 that provides an indication that the input mechanism 7002 isengaged optionally provides dynamic visual feedback that has acharacteristic based on a current progress of the user input 11044(e.g., speed, duration, number of repetitions, etc.). As shown in FIG.11Q, after the instruction user interface 11046 is displayed, user input11044 continues in accordance with the progress required for re-enablingthe disabled input mechanism and waking the display to the normaldisplay-on state. In some embodiments, as shown in FIG. 11R-11S, as theuser input 11044 continues in accordance with the progress required forre-enabling the disabled input mechanisms and waking the display to thenormal display-on state (e.g., showing the regular wake screen 11010 a)(e.g., continued rotation of the digital crown is detected, and thenumber of turns and rotation speed meet the preset criteria), touchscreen 712 is gradually lit-up showing a dimmed version 11010 b of theregular wake screen 11010 (e.g., as shown in FIG. 11R). In FIG. 11S, asthe touch-screen 712 is gradually lit-up to show a dimmed version 11010b of the regular wake screen 11010, the user input 11044 continues inaccordance with the progress required for re-enabling the disabled inputmechanisms and waking the display to the normal display-on state. InFIG. 11T, in accordance with a determination that the requirements areultimately met by the user input 11044, the device displays the regularwake screen 11010 a in the normal display-on state of the device 700.Once the input 11044 has met the criteria for turning on the display tothe regular wake screen 11010 in the normal display-on mode, the device700 also re-enables the disabled input mechanisms, and the user canoperate the device 700 in the manner as described in FIGS. 11C-11H, andaccompanying descriptions. Optionally, the device 700 terminates thesleep mode and allow the device to be woken in the manner described inFIGS. 11A-11B in accordance with some embodiments.

FIGS. 11U-11X illustrate that, if the input on the input mechanism 7002does not fully meet (e.g., not enough number of turns, not fast enough,not continuous enough, etc.) the criteria for turning on the display tothe normal display-on state and re-enabling the disabled inputmechanisms, the device 700 returns to displaying the dark sleep screen11046 and does not re-enable the disabled input mechanisms at the end ofthe input. FIGS. 11U-11W are analogous to FIGS. 11O-11R. In FIG. 11U, auser input 11044 is detected on the input mechanism 7002, while the darksleep screen 11038 is displayed. In FIG. 11V, as the input mechanism7002 is engaged by the input 11044 on the input mechanism 7002, theinstruction user interface 11046 is displayed. In FIG. 11W, as the userinput 11044 continues to progress according to the requirements forre-enabling the disabled input mechanisms and waking the display to thenormal display-on state, the device displays a dimmed version 11010 b ofthe regular wake screen. However, as shown in FIG. 11X, the input 11044does not fully meet the criteria for exiting the mode in which thevarious input mechanisms are disabled and as a result, the device 700redisplays the dark sleep screen 11038 at the termination of the input11044, and the input mechanisms that were disabled remain disabled.

FIG. 11Y-11Z illustrate that, while in the sleep mode during the sleepperiod and while displaying the dark sleep screen 11038, the device 700detects movement data that is indicative of the user being awake. Inresponse to detecting the movement data and in accordance with adetermination that the user is awake, the device 700 displays an earlywake user interface 11052. In some embodiments, the early wake userinterface 11052 displays a message indicating that the user appears tobe awake, and prompting the user to manually terminate the sleep mode ifso desired. In some embodiments, the early wake user interface 11052includes a disable button 11054 and a cancel button 11056. In responseto activation of the disable button 11054 (e.g., by a tap input by acontact 11058), the device dismisses the early wake user interface,terminates the sleep mode, and enters into the normal operation modebefore the scheduled end time of the sleep period. If an alarm is setfor the end of the sleep period, the alarm is canceled, in someembodiments. After exiting the sleep mode, the normal wake screen 11010a is displayed and the disabled input mechanisms are all re-enabled. Ifthe cancel button 11056 is activated, the device 700 remains in thesleep mode and the dark sleep screen 11038 is redisplayed, and thedisabled input mechanisms remain disabled until the end of the sleepperiod is reached and the device 700 exits the sleep mode automatically.In some embodiments, the early wake user interface 11052 is displayed inresponse to detecting a specific gesture. In some embodiments, the earlywake user interface is displayed in response to detecting a specificgesture (e.g., a raise gesture) for a predetermined amount of time(e.g., 30 seconds). In some embodiments, the early wake user interfaceis displayed in response to detecting a user input that meets the set ofone or more predefined criteria (e.g., the set of one or more predefinedcriteria described above with reference to FIGS. 11O-11T). In someembodiments, the early wake user interface 11052 is displayed inresponse to detecting a user input that meets a second set of one ormore predefined criteria distinct (e.g., a set of one or more predefinedcriteria different from the set of one or more predefined criteriadescribed above with reference to FIGS. 11O-11T).

FIGS. 11AA-11AB illustrate that, an alarm that is scheduled to go offduring the sleep period of the active sleep schedule can break throughthe sleep mode and be displayed at the schedule alarm time, inaccordance with some embodiments. While the dark sleep screen 11038 isdisplayed while the sleep mode is active during the scheduled sleepperiod (e.g., as shown in FIG. 11AA), in accordance with a determinationthat a preset alarm time (e.g., 2:30 AM) is reached, the device 700replaces display of the dark sleep screen 11038 (e.g., in FIG. 11AA)with an alarm user interface 11060 and generates non-visual alarm outputin conjunction with displaying the alarm user interface 11060, as shownin FIG. 11AB. Even though most notifications are suppressed during thesleep mode (e.g., due to the operation of the DND mode), preset alarmsare still allowed to break through the sleep mode. In some embodiments,the alarm user interface 11060 includes a stop button 11062 and a snoozebutton 11064. The device 700 temporarily enables the touch screen toallow the user to input a selection of the buttons on the alarm userinterface 11060/. For example, through a user input 11066 on the stopbutton 11062, the alarm output is stopped, and the device 700 optionallyreturns to sleep mode and redisplays the dark sleep screen 11038. Insome embodiments, the sleep mode is terminated before its scheduled endtime in response to the inputs on the alarm user interface. In someembodiments, in response to the user dismissing the alarm user interface11060, the device enables the disabled input mechanisms for a presettime period without exiting the sleep mode.

FIGS. 11AC-11AF illustrates how the device 700 automatically exits thesleep mode and re-enables the disabled input mechanisms at the scheduledend time of the sleep period, in accordance with some embodiments. FIG.11AC shows that the device displays the dark sleep screen 11038 prior tothe scheduled end time of the sleep period. In FIG. 11AD, when thescheduled end time of the sleep period is reached, the device generatesthe alarm output for the wake alarm and replaces display of the darksleep screen with display of an alarm user interface 11068. The device700 also re-enables the disabled input mechanisms, e.g., at least thetouch-screen 712, in accordance with some embodiments. In someembodiments, the alarm user interface 10068 includes a stop button 11054and a snooze button 11056. FIG. 11AE illustrates that a user input 11058is detected on the stop button 11054 and in response to the input, thedevice 700 dismisses the alarm user interface 11068 and displays thegood morning screen 11070 that corresponds to a wind up period followingthe sleep period. In some embodiments, the good morning user interface11070 includes a weather display component 11072 and a battery leveldisplay component 11074. In some embodiments, the good morning userinterface 11070 includes other display components instead of, or inaddition to, the two components shown in FIG. 11AF. The good morninguser interface 11070 includes a dismiss button 11076 that, whenactivated, dismisses the good morning user interface 11070 and allowsthe user to interact with the device 700 in the normal operation mode(e.g., navigates to regular wake screen 11010 a from which the user caninteract with the device 700 using various input mechanisms that arere-enabled).

FIGS. 12A-12D are flowchart diagrams of a method 12000 of disabling andenabling an input mechanism of an electronic device during a scheduledrestricted mode, in accordance with some embodiments.

This method relates to transitioning the computer system into a secondmode in which the display is dark and unresponsive to normal wakinginputs (e.g., various input mechanisms are disabled) or remaining in afirst mode in which display can be woken using normal waking inputs,depending on whether the current time is during a sleep period of anactive sleep schedule. While in the second mode during the sleep period,the disabled input mechanisms can be enabled if one or morecharacteristics of detected user input detected using a still-enabledinput mechanism (e.g., digital crown of the watch) meet a set of one ormore predefined criteria (e.g., rotation by at least a preset number oftimes, etc.). Transitioning the computer system into the second mode orremaining in the first mode, depending on the characteristics of thefirst user input prevents the computer system to be accidentallyactivated, promotes sleep tracking and reduce distraction from thecomputer system. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

The method 12000 is performed at a computer system (e.g., a portableelectronic device such as a mobile phone or tablet device, a wearableelectronic device, such as a watch or bracelet, etc.) in communicationwith a first input mechanism and a second input mechanism. In someembodiments, the first input mechanism comprises a touch-sensitivedisplay, and the second input mechanism comprises a mechanical inputdevice, such as a dial, button, switch, etc. In some embodiments, thefirst input mechanism includes motion sensors and/or vibration sensorscoupled to the computer system. In some embodiments, the computer systemis also in communication with other input mechanisms different from thefirst and second input mechanisms. In accordance with a determinationthat a current time is within a first scheduled sleep time period of anactive sleep schedule, the computer system configures (12002) thecomputer system to operate in a first mode (e.g., sleep mode, with DNDturned on and screen turned off or shown with simplified user interfaceand reduced luminance, etc.), wherein user input selecting an affordanceusing the first input mechanism (e.g., because the touch-screen is darkand/or not displaying an activatable user interface object) is disabledin the first mode. While the electronic system is in the first mode, thecomputer system detects (12004), via the second input mechanism, firstuser input. In accordance with a determination that one or morecharacteristics of the first user input meet a set of one or morepredefined criteria (e.g., the one or more characteristics of the inputinclude a speed of a rotation, a duration of the rotation, a directionof the rotation, a magnitude of the rotation or a combination thereof),the computer system transitions (12006) the computer system into asecond mode different from the first mode, wherein user input selectingan affordance using the first input mechanism is enabled in the secondmode; and in accordance with a determination that the one or morecharacteristics of the first user input do not meet the set of one ormore predefined criteria, the computer system remains (12008) in thefirst mode and foregoes transitioning the computer system into thesecond mode.

In some embodiments, configuring the computer system to operate in thefirst mode includes (12010) at least partially disabling multiple inputmechanisms in communication with the computer system, except the secondinput mechanism. In some embodiments, the computer system is incommunication with the touch sensors coupled to the display, motionsensors enclosed in the housing, and optionally, activation sensorscoupled to hardware or solid state buttons on the housing. In someembodiments, in the second mode, the computer system is configured todetect and disambiguate different types of touch inputs (e.g., tap,double tap, long press, hard press, upward swipe, downward swipe,leftward swipe, rightward swipe, fast swipe, slow swipe, edge swipe froma first edge, edge swipe from a second edge, etc.) detected by the touchsensors, while in the first mode, the computer system does not performtouch gesture recognition to disambiguate the different types of touchinputs. The computer system optionally recognizes that touch inputs havebeen detected by the touch sensors, but do not respond to the touchinputs in different ways based on the different input types as it doesin the second mode. In some embodiments, in the second mode, a singletap input wakes the display of the computer system, but in the firstmode, a threshold number of touch inputs is required to wake the displayto show a prompt about the required input to unlock the device. In someembodiments, motion detected by the motion sensors cause the computersystem to wake the device in the second mode, but the same motiondetected by the motion sensors do not wake the device when the device isin the first mode. In some embodiments, different types of inputs on thebuttons on the housing of the computer system are recognized and used tocause different operations to be performed in the second mode. In thefirst mode, the computer system does not disambiguate the differenttypes of inputs on the buttons, and activation of the buttons in anymatter causes display of the prompt regarding the required input tounlock the device. In some embodiments, the touch-sensitive display doesnot wake in response to any user input after the computer systemtransitions to the first mode (e.g., the display remains dark unless thedigital crown is turned). Partially disabling multiple input mechanismsin communication with the computer system, except the second inputmechanism, when the computer system operates in the first mode, performsan operation when a set of conditions has been met without requiringfurther user input. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, configuring the computer system to operate in thefirst mode includes (12012) maintaining a display generation componentof the computer system (e.g., a touch-sensitive display, an LED display,etc.) in an inactive or low power state while the computer systemremains in the first mode. In some embodiments, the touch-sensitivedisplay wakes to a dim low power state from a dark state in response tothe first user input after the computer system transitions to the firstmode, then remains dim in response to subsequent user inputs as long asthe computer system remains in the first mode. In some embodiments, thetouch-sensitive display does not wake in response to any user inputafter the computer system transitions to and remains in the first mode.In some embodiments, dimming the touch-sensitive display includesturning the touch-sensitive display off completely. In some embodiments,the low power state has reduced luminance, and simplified appearancewith fewer user interface objects, as compared to the normal appearanceof the display in the second mode. In some embodiments, inactive stateis completely dark. In some embodiments, the low power state and theinactive state of the display in the first mode are not responsive todifferent types of touch gestures in different manners as it would inthe second mode. This is shown in FIGS. 11M-11N, for example, where thecomputer system (e.g., the peripheral device 700) maintains a displaygeneration component in an inactive or low power state (e.g., the darkstate user interface 11038) while the computer system remains in thefirst mode (e.g., in response to detecting user inputs shown in FIG.11M). Maintaining the display generation component of the computersystem in the active or low power state while the computer systemremains in the first mode performs an operation when a set of conditionshas been met without requiring further user input. Performing anoperation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the set of one or more predefined criteria (e.g.,criteria that prevent accidental activation of the computer system)includes (12014) a requirement for a characteristic movement (e.g.,rotation in a first direction by a first threshold number of turns,pressing consecutively a threshold number of times, etc.) of the secondinput mechanism (e.g., a watch crown, a button, etc.). In someembodiments, the requirement for the characteristic movement of thesecond input mechanism includes one or more of a required speed of themovement, a required duration of the movement, a required magnitude ofthe movement, a required movement pattern of the movement, a requiredquantity of a repeated movement, etc. This is shown in FIGS. 11O-11T,for example, where the set of one or more predefined criteria includes arequirement for a characteristic movement (e.g., rotation of themechanism 7002 by the user input 10044 a-c). Requiring thecharacteristic movement of the second input mechanism to meet the set ofone or more predefined criteria provides improved gesture for performingan operation, which reduces the number of inputs needed to perform anoperation enhances the operability of the device, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, while detecting, via the second input mechanism,the first user input, in accordance with a determination that a currentprogress of the first user input at least partially meets the set of oneor more predefined criteria (e.g., turning in the correct direction, butnot yet enough number of turns; the correct type of movement, but notyet enough magnitude, etc.), the computer system outputs (12016) (e.g.,displaying) an indication (e.g., static visual feedback, dynamic visualfeedback that has a characteristic that is based on a current progressof the first user input (e.g., speed, duration, number of repetitions,etc.), etc.) (e.g., a haptic) that the second input mechanism is engagedon a display generation component in communication with the computersystem. In some embodiments, the indication that the second inputmechanism is engaged includes instructions regarding the set of the oneor more predefined criteria that must be met to transition to the secondstate (e.g., the speed of a rotation, the direction of the rotation, themagnitude of the rotation, or a combination thereof). In someembodiments, the visual brightness of the indication scales with thecharacteristic of the first user input. For example, the indicationoptionally increases in brightness as the magnitude or number ofrepetitions of the rotation increases. This is shown in FIG. 11P, forexample, where in accordance with a determination that a currentprogress of the first user input (e.g., user input 11044 a) at leastpartially meets the set of one or more predefined criteria, (e.g.,turning the second mechanism in the correct direction, but not yetreaching the required number of turns; the correct type of movement, butat a lesser magnitude, etc.), the computer system outputs an indication(e.g., the instruction user interface 11046) that the second inputmechanism is engaged. Outputting an indication that the second inputmechanism is engaged on the display generation component incommunication with the computer system, while detecting the first inputand in accordance with the determination that the current progress ofthe first user input at least partially meets the set of one or morepredefined criteria, provides improved visual feedback to the user.Providing improved visual feedback enhances the operability of thedevice and makes the user-device interface more efficient, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system detects (12018) termination ofthe first user input. In response to detecting the termination of thefirst user input, in accordance with a determination that the one ormore characteristics of the first user input do not meet the set of oneor more predefined criteria, the computer system ceases to output theindication that the second input mechanism is engaged on the displaygeneration component (and remaining in the first mode). In someembodiments, the computer system ceases to display the indication thatthe second input mechanism is engaged in accordance with a determinationthat that the one or more characteristics of the first user input do notmeet the set of one or more predefined criteria within a predeterminedtime period (e.g., even if the first input is ongoing or stilldetected). This is shown in FIGS. 11U-11X, for example, where thecomputer system (e.g., the peripheral device 700) detects termination ofthe first user input (e.g., the user input 11044) and in response,ceases to output the indication that the second input mechanism isengaged (e.g., ceasing to display the instruction user interface 11046in FIG. 11V). Ceasing to output the indication that the second inputmechanism is engaged on the display generation component, in response todetecting the termination of the first user input and in accordance withthe determination that the one or more characteristics of the first userinput do not meet the set of the one or more predefined criteria,performs an operation when a set of conditions has been met withoutrequiring further user input. Performing an operation when a set ofconditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, transitioning the computer system into the secondmode (e.g., because the one or more predefined criteria have been met bythe first user input (e.g., before or upon termination of the first userinput)) includes (12020) outputting (e.g., displaying, on thetouch-sensitive display) an indication that the computer system hastransitioned into the second mode (e.g., and/or that the first userinput, detected via the second input mechanism, has met the set of oneor more predefined criteria) (e.g., a haptic). Outputting the indicationthat the computer has transitioned in the second mode as the computersystem transitions into the second mode provides improved visualfeedback to the user. Providing improved visual feedback enhances theoperability of the device and makes the user-device interface moreefficient, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, in accordance with a determination that the currenttime is within a first scheduled sleep time period of an active sleepschedule and that one or more relocking criteria are met (e.g., nofurther user inputs are received during a preset period of time), thecomputer system transitions (12022) the computer system (back) into thefirst mode. During the scheduled sleep time period, the first mode is“sticky,” in that the computer system will return to the first mode ifrelocking criteria are met. For example, if the first mode is a sleepmode, and the second mode is a normal mode of operation, then the usermay transition the computer system from the sleep mode to the normalmode (e.g., by turning the watch crown). However, if relocking criteriaare met (e.g., the user goes back to sleep, and so no further userinputs are received during a preset period of time) during the scheduledsleep time period, the computer system transitions back to the sleepmode. Subsequently, the user must perform another user input that meetsthe set of one or more predefined criteria (e.g., turning the watchcrown again) in order to transition to the normal mode. Transitioningthe computer system into the first mode, in accordance with thedetermination that the current time is within the first scheduled sleeptime period of the active sleep schedule and one or more relockingcriteria are met, performs an operation when a set of conditions hasbeen met without requiring further user input. Performing an operationwhen a set of conditions has been met without requiring further userinput controls enhances the operability of the device, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination that the currenttime is within a preset time period preceding the first scheduled sleeptime period of the active sleep schedule (e.g., the preset time periodis a wind down period before the first scheduled sleep time period, thepreset time period is a period of time that starts before the start ofthe wind down period and ends before the start of the first scheduledsleep time period (e.g., the preset time period starts 10 minutes beforethe start of the wind down period, and ends 10 minutes before the startof the first scheduled sleep time period), etc.), the computer systemdisplays (12024) a reminder to charge the computer system (and/or tocharge a companion device of the computer system). In some embodiments,the reminder to charge the computer system (and/or to charge a companiondevice of the computer system) is displayed in accordance with adetermination that the charge level of the computer system (or thecompanion device) is below a first preset threshold value (e.g., a fixed(e.g., 30%) battery power, or a dynamically determined threshold batterylevel, etc.). In some embodiments, the computer system does not displaythe reminder to charge the computer system if the charge level dropsbelow the first preset threshold value within a short time immediatepreceding the first scheduled sleep time period of the active sleepschedule (e.g., there is a gap (e.g., 10 minutes, 20 minutes, etc.)between the preset time period preceding the first scheduled sleep timeperiod and the first scheduled sleep time period). This prevents thereminder from creating unnecessary stress by not displaying when thereis minimal time remaining to charge the computer system before theschedule sleep time. In some embodiments, at the start of the presettime period preceding the first scheduled sleep time period, thecomputer system displays a notification indicating that the wind downperiod is about to start, and optionally a reminder for the user tocharge the computer system or its companion device. In some embodiments,a reminder screen is displayed instead of the notification, and thereminder screen serves as a screen-lock user interface and has to bedismissed with a predefined input in order for the wind down screen tobe displayed. This is shown in FIG. 7C, for example, where the currenttime is within a preset time period (e.g., one hour) preceding the firstscheduled sleep time period (e.g., the bedtime) and the computer system(e.g., the peripheral device 700) displays a reminder to charge thecomputer system (e.g., the charging reminder 7013). Displaying thereminder to charge the computer system, in accordance with thedetermination that the current time is within the preset time periodpreceding the first scheduled sleep time period of the active sleepschedule, performs an operation when a set of conditions has been metwithout requiring further user input. Performing an operation when a setof conditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the computer system (e.g., watch) is in thefirst mode, and in accordance with a determination that the current timeis an end time of the first scheduled sleep time period of the activesleep schedule, the computer system generates (12026) an alarm output(e.g., an audio output, a tactile output, and/or a visual output, etc.)indicating that the end time of the first scheduled sleep time periodhas been reached, wherein another alarm output indicating that the endtime of the first scheduled sleep time period has been reached isprovided on a companion device (e.g., mobile phone or tablet device) ofthe computer system with a delayed relative to the alarm outputgenerated at the computer system. In some embodiments, in response todismissing an alarm indication (e.g., turning the alarm off), thecomputer system transitions into the second mode (e.g., exiting thesleep mode). This is shown in FIGS. 7H-7I, for example, where thecomputer system (e.g., the peripheral device 700) is in the first mode(e.g., the sleep mode) and generates an alarm output (e.g., the alarmscreen 7030 in FIG. 7H) and another alarm is provided on a companiondevice (e.g., the portable multifunction device 100 in FIG. 7I) delayedrelative to the alarm output generated at the computer system.Generating the alarm output indicating that the end of time of the firstscheduled sleep time period has been reached, in accordance with thedetermination that the current time is the end time of the firstscheduled sleep time period of the active sleep schedule and thecomputer system is in the first mode, performs an operation when a setof conditions has been met without requiring further user input.Performing an operation when a set of conditions has been met withoutrequiring further user input controls enhances the operability of thedevice, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, activating a snooze function associated with thealarm output on either one of the computer system and the companiondevice causes (12028) a snooze function for the other of the computersystem and the companion device. This is shown in FIG. 7I, for example,where activating the snooze button 7034 on the peripheral device 700causes a snooze function for the portable multifunction device 100.Causing the snooze function for the other of the computer system and thecompanion device, when activating the snooze function associated withthe alarm output on either one of the computer system and the companiondevice, performs an operation when a set of conditions has been metwithout requiring further user input. Performing an operation when a setof conditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, dismissing the alarm output on either one of thecomputer system and the companion device causes (12030) dismissal of thealarm output on the other of the computer system and the companiondevice. This is shown in FIG. 7I-7J, for example, where activating thestop button 7032 on the peripheral device 700 causes a dismissal of thealarm output of the portable multifunction device 100. Causes thedismissal of the alarm output on the other of the computer system andthe companion, when dismissing the alarm output on either one of thecomputer system and the companion device, performs an operation when aset of conditions has been met without requiring further user input.Performing an operation when a set of conditions has been met withoutrequiring further user input controls enhances the operability of thedevice, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, if the alarm output on either one of the computersystem and the companion device is not generated due to low batterylevel at said one of the computer system and the companion device, thealarm output is (12032) still generated at the other of the computersystem and the companion device. Generating the alarm output at theother of the computer system and the companion device, despite one ofthe computer system and the companion device is in low battery level andfails to generate an alarm output, performs an operation when a set ofconditions has been met without requiring further user input. Performingan operation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, if the computer system ceases to be coupled to thecompanion device before the end time of the first scheduled sleep timeperiod is reached, the alarm output is (12034) generated at thecompanion device without the delay. Generating the alarm output at thecompanion device without the delay if the computer system ceases to becoupled to the companion device before the end time of the firstscheduled sleep time period is reached, performs an operation when a setof conditions has been met without requiring further user input.Performing an operation when a set of conditions has been met withoutrequiring further user input controls enhances the operability of thedevice, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, in accordance with a determination that the currenttime is after an end time of the first scheduled sleep time period ofthe active sleep schedule and that the computer system has transitionedinto the second mode (e.g., in response to the user dismissing the alarmoutput that was generated in response to reaching the end of the firstscheduled sleep time period, and/or in response to the user dismissingthe good morning screen after dismissing the alarm output, etc.), thecomputer system displays (12036) a reminder for charging the computersystem (e.g., displaying a current battery level and/or a reminder tocharge the computer system). This is shown in FIG. 11AF, for example,where the current time is after an end time of the first scheduled sleeptime period (e.g., alarm at 6:30) and the computer system (e.g., theperipheral device 700) displays a reminder for charging the computersystem (e.g., the battery level display component 11074). Displaying thereminder for charging the computer system, in accordance with thedetermination that the current time is after the end time of the firstscheduled sleep time period of the active sleep schedule and that thecomputer system has transitioned into the second mode, performs anoperation when a set of conditions has been met without requiringfurther user input. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, in accordance with a determination that the currenttime is after an end time of the first scheduled sleep time period ofthe active sleep schedule and that the computer system has transitionedinto the second mode (e.g., in response to the user dismissing the alarmoutput that was generated in response to reaching the end of the firstscheduled sleep time period, and/or in response to the user dismissingthe good morning screen after dismissing the alarm output, etc.), thecomputer system displays (12038) one or more notifications based onrecorded sleep data for multiple consecutive days of the active sleepschedule that indicate satisfaction of a preset sleep goal. In someembodiments, the coaching notifications provide positive feedback (e.g.,meeting certain sleep-related goals) only, and does not provide thenotification if the sleep goals are not met on consecutive number ofdays. In some embodiments, the coaching notifications provide areas andsuggestions for improvement. In some embodiments, the coachingnotifications are based on stored data relating to the active sleepschedule (e.g., number of days a user has successfully adhered to theactive sleep schedule, whether the user has consistently gone to bed onor before the scheduled sleep time period, whether the user has skippedwind down periods, etc.). This is shown in FIG. 5T, for example, wherethe computer system (e.g., the portable multifunction device 700)displays one or more notifications based on recorded sleep data formultiple consecutive days (e.g., the weekly summary data 5108 thatdescribes meeting the sleep goal for five of the last seven days).Displaying the one or more notifications based on recorded sleep datafor multiple consecutive days of the active sleep schedule, inaccordance with the determination that the current time is after the endtime of the first scheduled sleep time period and the computer systemhas transitioned into the second mode, performs an operation when a setof conditions has been met without requiring further user input.Performing an operation when a set of conditions has been met withoutrequiring further user input controls enhances the operability of thedevice, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments: in accordance with a determination that the currenttime is after an end time of the first scheduled sleep time period ofthe active sleep schedule and that the computer system has transitionedinto the second mode (e.g., in response to the user dismissing the alarmoutput that was generated in response to reaching the end of the firstscheduled sleep time period, and/or in response to the user dismissingthe good morning screen after dismissing the alarm output, etc.), thecomputer system displays (12040) one or more notifications based onrecorded sleep data for the previous day that indicate satisfaction of apreset sleep goal. This is shown in FIG. 5R, for example, where thecomputer system (e.g., the portable multifunction device) displays oneor more notifications based on recorded sleep data for the previous daythat indicate satisfaction of a preset sleep goal (e.g., thenotification 5098). Displaying the one or more notifications based onrecorded sleep data for the previous day that indicate satisfaction of apreset sleep goal, in accordance with the determination that the currenttime is after the end time of the first scheduled sleep time period andthat the computer system has transitioned into the second mode, performsan operation when a set of conditions has been met without requiringfurther user input. Performing an operation when a set of conditions hasbeen met without requiring further user input controls enhances theoperability of the device, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, configuring the computer system to operate in thefirst mode includes (12042) maintaining a Do Not Disturb mode of thecomputer system and displaying, on a display generation component incommunication with the computer system, a visual indicator of the Do NotDisturb mode (e.g., a DND indicator). This is shown in FIG. 11M, forexample, where the computer system displays a visual indicator of the DoNot Disturb mode (e.g., the DND indicator 11040). Maintaining the Do NotDisturb mode of the computer system and displaying the visual indicatorof the Do Not Disturb mode on the display generation component incommunication with the computer system, when the computer system isoperating in the first mode, performs an operation when a set ofconditions has been met without requiring further user input. Performingan operation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system detects (12044) inputsindicative of an activity level of a user of the computer system duringthe first scheduled sleep time period of the active sleep schedule. Inaccordance with a determination that the inputs correspond to a wakestate of the user, and that the current time is before an end time ofthe first scheduled sleep time period of the active sleep schedule, thecomputer system displays a user interface through which selecting anaffordance using the first input mechanism is temporarily enabled,wherein the user interface provides a first affordance, when activatedthrough the first input mechanism, preemptively cancels an alarm output(e.g., an audio output, a tactile output, and/or a visual output, etc.)scheduled to go off at the end time of the first scheduled sleep timeperiod. In some embodiments, the computer system detects an input thatactivates the first affordance using the first input mechanism, andforgoes generating the alarm output when the end time of the firstscheduled sleep time period is reached. In some embodiments, thecomputer system, in response to detecting the input that activates thefirst affordance using the first input mechanism, transitioning into thesecond mode before the end time of the first scheduled sleep time periodis reached. This is shown in FIG. 11Z, for example, where the computersystem (e.g., the peripheral device 700) detects inputs indicative of anactivity level of a user and provides the first affordance (e.g., theearly wake user interface 11052) that, when activated through the firstinput mechanism (e.g., the disable button 11054), preemptively cancelsan alarm output scheduled to go off at the end time of the firstscheduled sleep time period. Preemptively canceling the alarm outputscheduled to go off at the end time of the first scheduled sleep timeperiod, when activing the first accordance through the first inputmechanism, performs an operation when a set of conditions has been metwithout requiring further user input. Performing an operation when a setof conditions has been met without requiring further user input controlsenhances the operability of the device, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the user interface provides (12046) a secondaffordance, when activated through the first input mechanism, dismissesthe user interface without canceling the alarm output scheduled to gooff at the end time of the first scheduled sleep time period. In someembodiments, the computer system detects an input that activates thesecond affordance using the first input mechanism, and returns to thefirst mode, forgoes transitioning into the second mode before the endtime of the first scheduled sleep time period. In some embodiments, thecomputer system generates the alarm output when the end time of thefirst scheduled sleep time period is reached. In some embodiments, if noinput is received through the user interface within the threshold amountof time since display of the user interface, the computer system ceasesto display the user interface and disables the first input mechanism.This is shown in FIG. 11Z, for example, where the second affordance(e.g., the cancel button 11056), when activated, dismisses the userinterface (e.g., the early wake user interface 10052) without cancelingthe alarm output scheduled to go off at the end time of the firstscheduled sleep time period. Dismissing the user interface withoutcanceling the alarm output scheduled to go off at the end time of thefirst scheduled sleep time period, when activating the second affordancethrough the first input mechanism, performs an operation when a set ofconditions has been met without requiring further user input. Performingan operation when a set of conditions has been met without requiringfurther user input controls enhances the operability of the device,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

Note that details of the processes described above with respect to eachof methods 6000, 8000, 10000, and 12000 are also applicable in ananalogous manner to the other methods described below/above. Forexample, method 6000 optionally includes one or more of thecharacteristics of the various methods described above with reference tomethod 8000, 10000, and 12000. For example, the sleep schedules, sleepperiods, wind down periods, wind up periods, wake times, alarms, winddown screens, sleep screens, good morning screens, restricted modes,low-power modes, wake screens, input mechanisms, etc. share similarcharacteristics in the different methods 6000, 8000, 10000, 12000, invarious embodiments, unless otherwise specified. For brevity, thesedetails are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, twitter IDs,home addresses, data or records relating to a user's health or level offitness (e.g., vital signs measurements, medication information,exercise information, etc.), date of birth, or any other identifying orpersonal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables users tocalculated control of the delivered content. Further, other uses forpersonal information data that benefit the user are also contemplated bythe present disclosure. For instance, health and fitness data may beused to provide insights into a user's general wellness, or may be usedas positive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide mood-associated data for targetedcontent delivery services. In yet another example, users can select tolimit the length of time mood-associated data is maintained or entirelyprohibit the development of a baseline mood profile. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

What is claimed is:
 1. A method, comprising: at a computer system incommunication with a first input mechanism and a second input mechanism:in accordance with a determination that a current time is within a firstscheduled sleep time period of an active sleep schedule, wherein thefirst scheduled sleep time period specifies a bedtime and a wake timefor a user, configuring the computer system to operate in a first mode,wherein user input selecting an affordance using the first inputmechanism is disabled in the first mode; while the computer system is inthe first mode, detecting, via the second input mechanism, first userinput; while detecting, via the second input mechanism, the first userinput: in accordance with a determination that a current progress of thefirst user input at least partially meets a set of one or morepredefined criteria, outputting an indication that the second inputmechanism is engaged on a display generation component in communicationwith the computer system; in accordance with a determination that one ormore characteristics of the first user input meet the set of one or morepredefined criteria, transitioning the computer system into a secondmode different from the first mode, wherein user input selecting anaffordance using the first input mechanism is enabled in the secondmode; in accordance with a determination that the one or morecharacteristics of the first user input do not meet the set of one ormore predefined criteria, remaining in the first mode and foregoingtransitioning the computer system into the second mode; detectingtermination of the first user input; and in response to detecting thetermination of the first user input, in accordance with a determinationthat the one or more characteristics of the first user input do not meetthe set of one or more predefined criteria, ceasing to output theindication that the second input mechanism is engaged on the displaygeneration component.
 2. The method of claim 1, wherein configuring thecomputer system to operate in the first mode includes at least partiallydisabling multiple input mechanisms in communication with the computersystem, except the second input mechanism.
 3. The method of claim 1,wherein configuring the computer system to operate in the first modeincludes maintaining the display generation component of the computersystem in an inactive or low power state while the computer systemremains in the first mode.
 4. The method of claim 1, wherein the set ofone or more predefined criteria includes a requirement for acharacteristic movement of the second input mechanism.
 5. The method ofclaim 1, wherein transitioning the computer system into the second modeincludes outputting an indication that the computer system hastransitioned into the second mode.
 6. The method of claim 1, comprising:in accordance with a determination that the current time is within afirst scheduled sleep time period of an active sleep schedule and thatone or more relocking criteria are met, transitioning the computersystem into the first mode.
 7. The method of claim 1, comprising: inaccordance with a determination that the current time is within a presettime period preceding the first scheduled sleep time period of theactive sleep schedule, displaying a reminder to charge the computersystem.
 8. The method of claim 1, comprising: while the computer systemis in the first mode, and in accordance with a determination that thecurrent time is an end time of the first scheduled sleep time period ofthe active sleep schedule, generating an alarm output indicating thatthe end time of the first scheduled sleep time period has been reached,wherein another alarm output indicating that the end time of the firstscheduled sleep time period has been reached is provided on a companiondevice of the computer system with a delay relative to the alarm outputgenerated at the computer system.
 9. The method of claim 8, whereinactivating a snooze function associated with the alarm output on eitherone of the computer system and the companion device causes a snoozefunction for the other of the computer system and the companion device.10. The method of claim 8, wherein dismissing the alarm output on eitherone of the computer system and the companion device causes dismissal ofthe alarm output on the other of the computer system and the companiondevice.
 11. The method of claim 8, wherein if the alarm output on eitherone of the computer system and the companion device is not generated dueto low battery level at said one of the computer system and thecompanion device, the alarm output is still generated at the other ofthe computer system and the companion device.
 12. The method of claim 8,wherein if the computer system ceases to be coupled to the companiondevice before the end time of the first scheduled sleep time period isreached, the alarm output is generated at the companion device withoutthe delay.
 13. The method of claim 1, comprising: in accordance with adetermination that the current time is after an end time of the firstscheduled sleep time period of the active sleep schedule and that thecomputer system has transitioned into the second mode, displaying areminder for charging the computer system.
 14. The method of claim 1,comprising: in accordance with a determination that the current time isafter an end time of the first scheduled sleep time period of the activesleep schedule and that the computer system has transitioned into thesecond mode, displaying one or more notifications based on recordedsleep data for multiple consecutive days of the active sleep schedulethat indicate satisfaction of a preset sleep goal.
 15. The method ofclaim 1, including: in accordance with a determination that the currenttime is after an end time of the first scheduled sleep time period ofthe active sleep schedule and that the computer system has transitionedinto the second mode, displaying one or more notifications based onrecorded sleep data for the previous day that indicate satisfaction of apreset sleep goal.
 16. The method of claim 1, wherein configuring thecomputer system to operate in the first mode includes maintaining a DoNot Disturb mode of the computer system and displaying, on the displaygeneration component in communication with the computer system, a visualindicator of the Do Not Disturb mode.
 17. The method of claim 1,including: detecting inputs indicative of an activity level of a user ofthe computer system during the first scheduled sleep time period of theactive sleep schedule; and in accordance with a determination that theinputs correspond to a wake state of the user, and that the current timeis before an end time of the first scheduled sleep time period of theactive sleep schedule, displaying a user interface through whichselecting an affordance using the first input mechanism is temporarilyenabled, wherein the user interface provides a first affordance, whenactivated through the first input mechanism, preemptively cancels analarm output scheduled to go off at the end time of the first scheduledsleep time period.
 18. The method of claim 17, wherein the userinterface provides a second affordance, that when activated through thefirst input mechanism, dismisses the user interface without cancelingthe alarm output scheduled to go off at the end time of the firstscheduled sleep time period.
 19. An electronic device in communicationwith a first input mechanism and a second input mechanism, theelectronic device comprising: a display generation component; one ormore processors; and memory storing one or more programs, wherein theone or more programs are configured to be executed by the one or moreprocessors, the one or more programs including instructions for: inaccordance with a determination that a current time is within a firstscheduled sleep time period of an active sleep schedule, wherein thefirst scheduled sleep time period specifies a bedtime and a wake timefor a user, configuring the electronic device to operate in a firstmode, wherein user input selecting an affordance using the first inputmechanism is disabled in the first mode; while the electronic device isin the first mode, detecting, via the second input mechanism, first userinput; while detecting, via the second input mechanism, the first userinput: in accordance with a determination that a current progress of thefirst user input at least partially meets a set of one or morepredefined criteria, outputting an indication that the second inputmechanism is engaged on the display generation component incommunication with the electronic device; in accordance with adetermination that one or more characteristics of the first user inputmeet the set of one or more predefined criteria, transitioning theelectronic device into a second mode different from the first mode,wherein user input selecting an affordance using the first inputmechanism is enabled in the second mode; in accordance with adetermination that the one or more characteristics of the first userinput do not meet the set of one or more predefined criteria, remainingin the first mode and foregoing transitioning the electronic device intothe second mode; detecting termination of the first user input; and inresponse to detecting the termination of the first user input, inaccordance with a determination that the one or more characteristics ofthe first user input do not meet the set of one or more predefinedcriteria, ceasing to output the indication that the second inputmechanism is engaged on the display generation component.
 20. Theelectronic device of claim 19, wherein configuring the electronic deviceto operate in the first mode includes at least partially disablingmultiple input mechanisms in communication with the electronic device,except the second input mechanism.
 21. The electronic device of claim19, wherein configuring the electronic device to operate in the firstmode includes maintaining the display generation component of theelectronic device in an inactive or low power state while the electronicdevice remains in the first mode.
 22. The electronic device of claim 19,wherein the set of one or more predefined criteria includes arequirement for a characteristic movement of the second input mechanism.23. The electronic device of claim 19, the one or more programsincluding instructions for: in accordance with a determination that thecurrent time is within the first scheduled sleep time period of theactive sleep schedule and that one or more relocking criteria are met,transitioning the computer system into the first mode.
 24. Theelectronic device of claim 19, the one or more programs includinginstructions for: in accordance with a determination that the currenttime is within a preset time period preceding the first scheduled sleeptime period of the active sleep schedule, displaying a reminder tocharge the computer system.
 25. The electronic device of claim 19, theone or more programs including instructions for: while the computersystem is in the first mode, and in accordance with a determination thatthe current time is an end time of the first scheduled sleep time periodof the active sleep schedule, generating an alarm output indicating thatthe end time of the first scheduled sleep time period has been reached,wherein another alarm output indicating that the end time of the firstscheduled sleep time period has been reached is provided on a companiondevice of the computer system with a delay relative to the alarm outputgenerated at the computer system.
 26. The electronic device of claim 25,wherein activating a snooze function associated with the alarm output oneither one of the computer system and the companion device causes asnooze function for the other of the computer system and the companiondevice.
 27. The electronic device of claim 25, wherein dismissing thealarm output on either one of the computer system and the companiondevice causes dismissal of the alarm output on the other of the computersystem and the companion device.
 28. The electronic device of claim 25,wherein if the alarm output on either one of the computer system and thecompanion device is not generated due to low battery level at said oneof the computer system and the companion device, the alarm output isstill generated at the other of the computer system and the companiondevice.
 29. The electronic device of claim 25, wherein if the computersystem ceases to be coupled to the companion device before the end timeof the first scheduled sleep time period is reached, the alarm output isgenerated at the companion device without the delay.
 30. The electronicdevice of claim 19, the one or more programs including instructions for:in accordance with a determination that the current time is after an endtime of the first scheduled sleep time period of the active sleepschedule and that the computer system has transitioned into the secondmode, displaying a reminder for charging the computer system.
 31. Theelectronic device of claim 19, the one or more programs includinginstructions for: in accordance with a determination that the currenttime is after an end time of the first scheduled sleep time period ofthe active sleep schedule and that the computer system has transitionedinto the second mode, displaying one or more notifications based onrecorded sleep data for multiple consecutive days of the active sleepschedule that indicate satisfaction of a preset sleep goal.
 32. Theelectronic device of claim 19, the one or more programs includinginstructions for: in accordance with a determination that the currenttime is after an end time of the first scheduled sleep time period ofthe active sleep schedule and that the computer system has transitionedinto the second mode, displaying one or more notifications based onrecorded sleep data for the previous day that indicate satisfaction of apreset sleep goal.
 33. The electronic device of claim 19, whereinconfiguring the computer system to operate in the first mode includesmaintaining a Do Not Disturb mode of the computer system and displaying,on the display generation component in communication with the computersystem, a visual indicator of the Do Not Disturb mode.
 34. Theelectronic device of claim 19, the one or more programs includinginstructions for: detecting inputs indicative of an activity level of auser of the computer system during the first scheduled sleep time periodof the active sleep schedule; and in accordance with a determinationthat the inputs correspond to a wake state of the user, and that thecurrent time is before an end time of the first scheduled sleep timeperiod of the active sleep schedule, displaying a user interface throughwhich selecting an affordance using the first input mechanism istemporarily enabled, wherein the user interface provides a firstaffordance, when activated through the first input mechanism,preemptively cancels an alarm output scheduled to go off at the end timeof the first scheduled sleep time period.
 35. A non-transitory computerreadable storage medium storing one or more programs, the one or moreprograms comprising instructions, which, when executed by an electronicdevice in communication with a first input mechanism and a second inputmechanism and having a display generation component, cause theelectronic device to: in accordance with a determination that a currenttime is within a first scheduled sleep time period of an active sleepschedule, wherein the first scheduled sleep time period specifies abedtime and a wake time for a user, configure the electronic device tooperate in a first mode, wherein user input selecting an affordanceusing the first input mechanism is disabled in the first mode; while theelectronic device is in the first mode, detect, via the second inputmechanism, first user input; while detecting, via the second inputmechanism, the first user input: in accordance with a determination thata current progress of the first user input at least partially meets aset of one or more predefined criteria, output an indication that thesecond input mechanism is engaged on the display generation component incommunication with the electronic device; in accordance with adetermination that one or more characteristics of the first user inputmeet the set of one or more predefined criteria, transition theelectronic device into a second mode different from the first mode,wherein user input selecting an affordance using the first inputmechanism is enabled in the second mode; in accordance with adetermination that the one or more characteristics of the first userinput do not meet the set of one or more predefined criteria, remain inthe first mode and foregoing transitioning the electronic device intothe second mode; detect termination of the first user input; and inresponse to detecting the termination of the first user input, inaccordance with a determination that the one or more characteristics ofthe first user input do not meet the set of one or more predefinedcriteria, cease to output the indication that the second input mechanismis engaged on the display generation component.
 36. The non-transitorycomputer readable storage medium of claim 35, wherein configuring theelectronic device to operate in the first mode includes at leastpartially disabling multiple input mechanisms in communication with theelectronic device, except the second input mechanism.
 37. Thenon-transitory computer readable storage medium of claim 35, whereinconfiguring the electronic device to operate in the first mode includesmaintaining the display generation component of the electronic device inan inactive or low power state while the electronic device remains inthe first mode.
 38. The non-transitory computer readable storage mediumof claim 35, wherein the set of one or more predefined criteria includesa requirement for a characteristic movement of the second inputmechanism.
 39. The non-transitory computer readable storage medium ofclaim 35, the one or more programs including instructions, which, whenexecuted by the electronic device, cause the electronic device to: inaccordance with a determination that the current time is within thefirst scheduled sleep time period of the active sleep schedule and thatone or more relocking criteria are met, transition the computer systeminto the first mode.
 40. The non-transitory computer readable storagemedium of claim 35, the one or more programs including instructions,which, when executed by the electronic device, cause the electronicdevice to: in accordance with a determination that the current time iswithin a preset time period preceding the first scheduled sleep timeperiod of the active sleep schedule, display a reminder to charge thecomputer system.
 41. The non-transitory computer readable storage mediumof claim 35, the one or more programs including instructions, which,when executed by the electronic device, cause the electronic device to:while the computer system is in the first mode, and in accordance with adetermination that the current time is an end time of the firstscheduled sleep time period of the active sleep schedule, generate analarm output indicating that the end time of the first scheduled sleeptime period has been reached, wherein another alarm output indicatingthat the end time of the first scheduled sleep time period has beenreached is provided on a companion device of the computer system with adelay relative to the alarm output generated at the computer system. 42.The non-transitory computer readable storage medium of claim 41, whereinactivating a snooze function associated with the alarm output on eitherone of the computer system and the companion device causes a snoozefunction for the other of the computer system and the companion device.43. The non-transitory computer readable storage medium of claim 41,wherein dismissing the alarm output on either one of the computer systemand the companion device causes dismissal of the alarm output on theother of the computer system and the companion device.
 44. Thenon-transitory computer readable storage medium of claim 41, wherein ifthe alarm output on either one of the computer system and the companiondevice is not generated due to low battery level at said one of thecomputer system and the companion device, the alarm output is stillgenerated at the other of the computer system and the companion device.45. The non-transitory computer readable storage medium of claim 41,wherein if the computer system ceases to be coupled to the companiondevice before the end time of the first scheduled sleep time period isreached, the alarm output is generated at the companion device withoutthe delay.
 46. The non-transitory computer readable storage medium ofclaim 35, the one or more programs including instructions, which, whenexecuted by the electronic device, cause the electronic device to: inaccordance with a determination that the current time is after an endtime of the first scheduled sleep time period of the active sleepschedule and that the computer system has transitioned into the secondmode, display a reminder for charging the computer system.
 47. Thenon-transitory computer readable storage medium of claim 35, the one ormore programs including instructions, which, when executed by theelectronic device, cause the electronic device to: in accordance with adetermination that the current time is after an end time of the firstscheduled sleep time period of the active sleep schedule and that thecomputer system has transitioned into the second mode, display one ormore notifications based on recorded sleep data for multiple consecutivedays of the active sleep schedule that indicate satisfaction of a presetsleep goal.
 48. The non-transitory computer readable storage medium ofclaim 35, the one or more programs including instructions, which, whenexecuted by the electronic device, cause the electronic device to: inaccordance with a determination that the current time is after an endtime of the first scheduled sleep time period of the active sleepschedule and that the computer system has transitioned into the secondmode, display one or more notifications based on recorded sleep data forthe previous day that indicate satisfaction of a preset sleep goal. 49.The non-transitory computer readable storage medium of claim 35, whereinconfiguring the computer system to operate in the first mode includesmaintaining a Do Not Disturb mode of the computer system and displaying,on the display generation component in communication with the computersystem, a visual indicator of the Do Not Disturb mode.
 50. Thenon-transitory computer readable storage medium of claim 35, the one ormore programs including instructions, which, when executed by theelectronic device, cause the electronic device to: detect inputsindicative of an activity level of a user of the computer system duringthe first scheduled sleep time period of the active sleep schedule; andin accordance with a determination that the inputs correspond to a wakestate of the user, and that the current time is before an end time ofthe first scheduled sleep time period of the active sleep schedule,display a user interface through which selecting an affordance using thefirst input mechanism is temporarily enabled, wherein the user interfaceprovides a first affordance, when activated through the first inputmechanism, preemptively cancels an alarm output scheduled to go off atthe end time of the first scheduled sleep time period.